[gutsy] failed to initialize hal

I /can't/ say if it is related, but it is impossible for me to update a tribe 5 installation today.

Everything is blocked while upgrading hal to version 0.5.9.1-ubuntu6 ; I got this message :

"Failed to open connection to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
invoke-rc.d: initscript dbus action "force-reload" failed".

Well, it is all working fine now, with Gutys latest updates (as in 091107)

I also having the same problem. Mine is not consistent, sometime OK, sometime it failed. Any solution for this?

Not seeing it anymore ? Is this bug "dead" ?

i just updated today(10/4/07) and now when i start in gnome i get 'failed to initialize HAL' and cant get a wired internet connection

I have the same problem after updating today 10/4/07. Now the get the 'failed to initialize HAL'.
My battery monitor doesn't work, nm-applet broken, and I can't start various menus in system->preferences such as power management.

Same problem here, any pointers to where to start debugging this?

First login to gnome gives Error: Failed to initialize HAL

if I restart dbus and logout/login everything seems to work.

I've managed to fix it with

sudo -i
cd /etc/rc2.d
ln -s S10dbus ../init.d/dbus
rm S50dbus

I'm not sure why HAL is S12hal and dbus was S50dbus when HAL needs dbus to function.

I wonder what the proper fix is?

CONCURRENCY=shell in /etc/init.d/rc caused the problem for me, I had to set it back to CONCURRENCY=none and my problem was solved for gutsy beta

Same problem here... I have the message after login to session. It is every time.

This bug has been in many Ubuntu versions. From research, I can just say that you should:

Copy the file "S12dbus" from /etc/rc3.d/ to /etc/rc2.d/ (If "S12dbus" is not already in /etc/rc2.d/).

If that does not work, try "sudo dpkg-reconfigure hal" (without the quotes) in a terminal.

If you try either of these ways, I recommend you restart to see if the message stops appearing and that you can connect to the internet.

If that does not work either, then you may have to type this in a terminal each time you use your computer:

"sudo /etc/init.d/dbus restart" (without the quotes)

Same problem here too... with the beta version of Hardy since the update from kernel 2.6.24.12 to 2.6.24.15. If I start with kernel 2.6.24.12, I have not problem. But If I start with kernel 2.6.24.15 -> "failed to initialize HAL" and no internet conection ......
Only "sudo /etc/init.d/dbus restart" works for me.

I recently upgraded from Ubuntu 7.10 to 8.04 beta using kernel 2.6.24.16. Ever since then I've been receiving a "failed to initialize HAL" error upon entering Gnome. This apparently prevents me from accessing my wifi card and mounting my Windows partitions, among other things. I regain HAL when I booted up with my Gutsy Kernel 2.4.22.14.

Based on what I've read here, it seems to be a problem with the kernel, as people started experiencing this when they upgraded their kernel.

I had the same issue after I removed the dbus from the Servcies Settings. Resolved the issue by copying the file "S12dbus" from /etc/rc3.d/ to /etc/rc2.d/

I encountered the same here, solution for me was removing the cache file; Open a terminal and crack up those fingers ;) sudo rm /var/cache/hald/fdi-cache, and 'touch' it again. sudo touch /var/cache/hald/fdi-cache than sudo dpkg-reconfigure hal and there it is. If all is ok, as it was for me... the last command must end in starting the hal daemon.