Description of problem: New Fedora 9 install, upgrade from Core 6 HAL daemon start fails during boot HAL can be manually started using the Gnome Services tool Version-Release number of selected component (if applicable): Latest as of 6/23/2008 How reproducible: Reboot machine; fails every time Steps to Reproduce: 1. 2. 3. Actual results: HAL fails to start during boot, but can be manually started later Expected results: I expect HAL to start during boot like it's supposed to. Additional info:
The problem stems from messagebus appearing after hald in /etc/rc.5 (thanks to BeLinux posting on Fedoraforums). The workaround is to rename the symbolic link for messagebus so it appears above the link for hald. I don't know why some newly installed systems, like mine, would end up with messagebus and hald in the wrong order in /etc/rc.5, but I think this makes this a genuine bug in Fedora 9.
Sean, Are you still running Fedora 9, or have you upgraded to 10 or Rawhide? In either case, can you let us know whether the issue is still happening, and give the current version of the HAL packages you're using? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Hi, I'm still using Fedora 9, and I fixed the problem a long time ago as I described in the note, by manually changing etc/rc.5. I don't know whether the new upgrades or installs will fix the problem, but at least I know how to manually fix it when I upgrade.
Sean, Thanks for your prompt response, from what I suspect this is an issue caused by upgrading from FC6 to F9. On my F9 system they are in the correct order as listed below: S05akmods S06cpuspeed S08ip6tables S08iptables S08nvidia S09isdn S11auditd S12restorecond S12rsyslog S13irqbalance S13rpcbind S14nfslock S15mdmonitor S18rpcidmapd S19rpcgssd S22messagebus S25fuse S25netfs S25pcscd S26acpid S26haldaemon S26udev-post S27NetworkManager S28setroubleshoot S50bluetooth S55sshd S58ntpd S80sendmail S90crond S90kerneloops S90smolt S95atd S96avahi-daemon S98cups S98wine S99anacron S99local As you can see messagebus is started before haldaemon, this system was a clean install of F9 not an upgrade. I do not have a copy of Fedora Core 6 to try an upgrade with so I am going to close this bug. If you should experience this issue again with a future release please open a new bug against the current version of the component. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers