I recreated the problem using hal package version 0.5.11~rc2-1ubuntu7
from Hardy. I then installed package version 0.5.11~rc2-1ubuntu8 from
hardy-proposed and the symlinks were set properly.
I did not use the CONCURRENCY=shell option as it wasn't clear to from
the test case what to look for.
** Description changed:
This seems to be a fairly common bug. However, none of the solutions I have
come
across in previous bug repors have helped me. When I run Ubuntu, just like
everyone else, I get
Failed to initalize HAL.
I can continue to use the GUI for a few minutes, but eventually (especially
when
navigating the filesystem/CD-ROM,) the system hangs and I am forced to reboot.
Though I am very new to Linux, I will help in the analysis in any way I
can.
TEST CASE:
- Set the rc.d symlinks to start level 12, to get to the situation many bug
reporters end up with for some reason:
sudo update-rc.d -f hal remove
- sudo update-rc.d hal start 12 2 3 4 5 . stop 12 1
+ sudo update-rc.d hal start 12 2 3 4 5 . stop 12 1 .
- (optional, since racy): Set CONCURRENCY=shell in /etc/init.d/rc, boot, and
watch hal fail to load
- upgrade to the new hardy-proposed version (0.5.11~rc2-1ubuntu8), check that
the rc symlinks are now at S24, and that the system boots properly with
CONCURRENCY=shell.
** Tags added: verification-done
** Tags removed: verification-needed
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
