Gusty Beta: error on startup. "Internal Error" "failed to initialize HAL!"

I also receive this error on startup after installation.

Same error here. I got it after installing the latest updates. Now my networkmanager says it has no connection; but there is one and i can just surf on the net. Pidgin on the other hand won't connect. On the Bottom of pidgin there's a message that says: Waiting for a network connection. I don't know if this is connection to the HAL error.

Same error since I've installed the Gutsy Beta: failed to initialize HAL on every startup, impossible to start hald, networkmanager and knetworkmanager not working, Brasero not working (the system can mount cdrom, I can use K3b or listen to CD with Kaffeine and Amarok, but not with Rhythmbox), occasionally error on gnome_netstatus applet. I tried to solve the "HAL problem" with a package downgrade (now I'm using the version 0.5.9-1ubuntu2-feisty backports), with "remove --purge hal" and reinstall and dpkg --configure -a without result

In the bug notification 147963 I found out a solution for HAL error it seams to work for me:
"...regenerating the cache works too:

   $ sudo /usr/lib/hal/hald-generate-fdi-cache
   15:00:38.314 [I] create_cache.c:611: Loading rules
   15:01:20.211 [I] create_cache.c:677: preprobe: offset=00000014, size=347312
   15:01:20.212 [I] create_cache.c:679: information: offset=00054cc4, size=117484
   15:01:20.212 [I] create_cache.c:681: policy: offset=000717b0, size=27916
   15:01:20.212 [I] create_cache.c:683: Generating rules done (occupying 492732 bytes)

Now hald service starts correctly"

As I restarted I hadn't any error, the services connected to gnome are working (cdrom mounting, volume and power manager and so on). The command "lshal" is working too and it seams recognize my hardware. I don't have the "hal" program i n /etc/init.d/ (so I don't know how to restart it just in case) and I still have to test network manager

I can confirm this bug. I got the exact same errors that Gelke got (Pidgin and everything). In addition, I can't connect to my Exchange server using evolution-exchange.

After using the suggestion from Giorgio, most of the functionality has come back, especially after restarting the HAL daemon. However, still cannot connect to Exchange server anymore.

Well, I restarted, and HAL is still giving me the same error: "Internat Error: Failed to initialize HAL!". I have to keep doing the same fix (from Giorgio, thanks by the way) every time I reboot and login. Everything seems to work okay after I do that. I believe now that the Exchange problem is unrelated, something else must have screwed it up, because I was able to fix it quickly by deleting some files in the ~/.evolution directory.

I don't want to have to stick "/usr/lib/hal/hald-generate-fdi-cache" into my /etc/rc.local file in order to get this working, I shouldn't have to do that. Anyone have any ideas as to what's changed?

For what it's worth:
I got this error on gutsy beta today, just after having modified /etc/init.d/rc with
CONCURRENCY=shell
instead of the previous
CONCURRENCY=none
(I wanted some more speed from my dual core :-)

I took the change back and the
"Internal Error" "failed to initialize HAL!"
disappeared.

I can confirm this. I did exactly that (change CONCURRENCY=none to CONCURRENCY=shell in /etc/init.d/rc) and that's when I got the "Failed to initialize HAL" error. I changed it back and everything was fine.

Same here. Changed to shell for faster booting, too fast as it seems. Well I hope this can be fixed soon, so that I can use this little tweak.

Same problem here... reverting the concurrency thing fixed it, but in all previous versions of kubuntu this didn't happen. Fix this bug.

same here (gutsy). Changing to CONCURRENCY=shell makes the error appear and changing it back makes it disappear

For solution, see: http://ubuntuguide.org/wiki/Ubuntu:Gutsy#HAL
Short answer: mv /etc/rc2.d/S50dbus /etc/rc2.d/S12dbus.

Fresh install of 8.04 on i686 laptop with no issues.

This issue started for me on apt install of Samba & DHCPd, I had bluetooth & wireless already on.

running init 5, boot would lock when loading samba with "Failed to initialize HAL". indefinite wait time.

I could <alt>F2 and login then restart dbus then startx and run normally.

turning samba & dhcpd off in services did not help.

All init scripts were correct and CONCURRENCY=none was set.
'sudo dpkg-reconfigure hal' did not help.

'$ sudo /usr/lib/hal/hald-generate-fdi-cache' was the only resolution that worked for me.

   Thanks everyone

I'm getting the same error message with jaunty-desktop-i386.iso (alpha4), selecting the install option, right after the desktop is loaded. But everything is unresponsive and I have to do a hard reset.
Not running in a VM, checked the ISO for consistency.

Thank you for taking the time to report this bug and helping to make Ubuntu better. I noticed that the package version your bugging is updated in Lucid. Please update via http://releases.ubuntu.com/lucid/ repost a detailed error report, and update the bug status. Thanks!

[Expired for hal (Ubuntu) because there has been no activity for 60 days.]