Oh dear. Please help! I was fixing something that wasn't really broken (well, its the fedora way, isn't it?
) and now lots of things seem to be broken.
When I now try to boot, it hangs on "Starting HAL daemon:" and never completes - it doesn't FAIL or do anything, it just hangs and I have to reboot and disable the haldaemon with chkconfig. What could be causing this haldaemon hang?
(Also, avahi-daemon won't start any more, and neither will console-kit - but at least they just fail and the boot process continues.)
The weird thing is, that once booted, I can start haldaemon, avahi-daemon, and console-kit without any problems using the Services gui in gnome. What gives? With this in mind I thought maybe I could get around the problem by making haldaemon start as a service in /etc/rc.local so it starts after everything else, but alas no, it still just hangs.
I *think* this started when I noticed that acpid was failing on boot with the error "Starting acpi daemon: acpid: can't open /proc/acpi/event: Device or resource busy". I figured this was because hald was using the resource, so I tried to make hald start AFTER acpid by making hald require acpid to start in the /etc/init.d/haldaemon. I then ran "chkconfig acpid resetpriorities". Since then I have had the problem described above. I have undone the changes i made in /etc/init.d/haldaemon and re-ran "chkconfig resetpriorities".
Any suggestions how I may fix my system? I "nearly" had it working properly before this latest mess-up!