Red Hat Bugzilla – Bug 181459
hal-device-manager take a long time to start up
Last modified: 2013-03-13 00:49:56 EDT
Description of problem:
hal-device-manager take a long time to start up.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I thought I fixed this with my last d-bus patch. It will be fixed upstream in
the D-Bus python bindings but it might have to show up as an fc5 update.
In addition to a slow start:
I believe there are some issues with other services that must be running. I'm
not sure which services are required apart from D-Bus? I created a launcher for
hal-device-manager but am getting the message that it can't get the device list,
make sure hal daemon is running. I wonder if there is a problem with the alias
for hald? I've noticed some instruction suggest starting with the command
"service 'hal daemon' but in the services list it is 'haldaemon' I've also got
other apps that are telling me to make sure hald is running (ie. volume manager
and sessions). hald is running and I've restarted it several times.
Daryl, please open another bug and provide more information like what version of
Fedora you are running and when did this start happening. This bug should be
closed as it is fixed in FC5 and Rawhide.