hald failed to initialize on start up, Gusty
Bug #157258 reported by
Johne
This bug report is a duplicate of:
Bug #149881: HAL fails to initialise when /etc/init.d/rc sets CONCURRENCY=shell.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hal (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
After starting up and logging in to GNOME i'm notified that hald has failed to initialize. This makes NetworkManager unable to work, being able to suspend from the logout screen is not possible , and any thing else that uses the hal daemon can not fully function. The current work around from me is to open up a console and run "sudo hald". I'm using and inspiron 1420n that i bought from dell preloaded with feisty, which i upgraded to gusty. I have add no new hardware, and this problem persists since i upgrade to gusty, across the 2.6.20 kernel (from feisty) to the newest gusty kernel. Thank you for your help in advance.
description: | updated |
To post a comment you must log in.
Reassigning to hal (was network-manager).
Let's find out what is the problem with your hald, hoping it will fix your network-manger problem.
I had that problem once, it was caused by me removing haldaemon, you may look at this by:
cat /etc/group|grep hal
and see if a line like:
haldaemon:x:116:
is there (can be an other number than 116).
That said, there can be many other causes.
Read bug #24029, and see what may apply to your case.
Please begin by " dmesg > ~/dmesg.log" ant then attach dmesg.log to this file.