internal error failed to initialize HAL

Same Happens to Me

Thank you for reporting this bug. However, it's a duplicate of bug 212271.

I believe this duplicate status is incorrect. saa7134-alsa module does not exist in lsmod. tried blacklisting anyway, as proposed in bug report 212271. The error still persisted. Please let me know what further info you need, would be pleased to help.

OK.
Would you please do the things that are described at <https://wiki.ubuntu.com/DebuggingHal>? This would help us very much.
Thanks in advance.

I have followed the instructions from the hal debugging guid. I will attach 3 files - hal.log, lshal.txt and kern.log.

I ran the commands:
sudo /etc/init.d/hal stop
sudo hald --verbose=yes --daemon=no 2>&1 | tee /tmp/hal.log

But the logging stopped almost immediately - see attached output.

I then tried the lshal command but this gave no output. I think this is not surprising as the hald command exited.
The kernel log is also attached in the next comment.

The wiki explains that the logging should start before the crash happens, but i believe the crash is during startup. Also trying to start hal "/etc/init.d/hal start" hangs.

I hope this is of help, please let me know if there is anything else i can provide.

Thanks.

I run Ubuntu 8.04 20080412 i386 generic

I stumble on the bug when I run
 -- linux-image-2.6.24-15 and
 -- linux-image-2.6.24-16.

The bug is not present on
 -- linux-image-2.6.24-14.

I was not able to run HAL from 2.6.24-16. I don't have Ethernet connexion nor good response in the Corba layer of Gnome. The window's menu is taking long to respond (5-10 seconds).

Thank you for your information. But it looks like kern.log is cut off. Are you sure it's complete? And are you sure that you ran hal as root? If the answer on both questions is yes, please attach /var/log/messages and /var/log/syslog, otherwise, please try again.

Apologies you are correct - i forgot sudo.

I will attach all files following this.

The kernel log however was trimmed at the start only for timestamp of previous day. reattached new full log.

Hope this is OK.

I can confirm this, just installed the brandnew RC of Hardy, and i get this after the first login (Network manager is disabled, so no internet connection)

http://img.xrmb2.net/images/679873.jpeg

This bug can be confirmed, since someone else is having the same problem and there are a lot of files attached. ;)
Maybe we need to give the developers more information, but I think it would be the best to let them see what is needed.
Thanks for the information you provided.

Thanks :D - just want to re confirm using the RC install disc - this bug is still present - and now in live CD, which is probably expected.
Any help will be gladly given.
Please let me know.
Regards,
Matt.

> I can confirm this, just installed the brandnew RC of Hardy, and i get this after the first login (Network manager is disabled, so no internet connection)

I can confirm this too. However, i "solved" this bug by removing my TV-card (Philips / Medion TV tuner + data/fax modem).

Without the TV-card, network is available again, no HAL-error, no delayed startup anymore and no desktop freeze.

This was with 64bit alternate CD (Hardy rc).

I can confirm the removal of my tv card (Phillips tuner) does indeed fix the problem. Replacing of the card repeats the problem.
Oh wait latest updates fixes the problem pertinently. :D Great job.

What happens next?

I have the same problem when I boot my computer. "Internal Error - Failed to initialize HAL!" when I login. Then I have all sorts of wrong behaviors like automounting not working.

If I then logout and log back in, everything is fine. It looks like a race condition described here: https://bugs.edge.launchpad.net/ubuntu/+source/hal/+bug/149881.

But I checked everything there and I my rc2 starting order are ok. In /etc/init.d/rc, CONCURRENCY is also set to none.

I have to say also that my connection preferences are set to "automatic". I'll try setting it back to manual. If it's a race issue, that may solve the problem.

Removing the automatic connection did solve the problem for me. So I confirm that it is a race condition here.

OK, somehow it works now for the reporter of the bug, so I'm marking it as invalid. Thank you for reporting it!
Martin Hamel: it looks like your problem is another bug. Would you please be so kind to file a new bug against HAL following the "How to file" procedure located at <https://wiki.ubuntu.com/DebuggingHal>.
Thanks!

I got the same problem as reported above:

"After logging into Gnome an error message appeared "Internal Error - Failed to initialize HAL!"
Networking was disabled, and took a very long time to logout."

Attached is my log files following the procedures at <https://wiki.ubuntu.com/DebuggingHal>.

Looking forward to solving this problem.
Cheers,
Alex

Marking Confirmed as the problem is still occurring with at least Alexandre. Checked with him offline and he doesn't have any saa* modules listed.

Note however that Alexandre doesn't have a TV card.

OK. Turns out Alexandre had his gdm starting up at S13 instead of S30 -- so he's seeing bug #227838.