[Bug 25931] Re: Failed to initalize HAL.

satkata satkata at web.de
Thu Nov 16 10:53:03 UTC 2006


Hi,

I have upgraded from Dapper to Edgy before a month or so and everything was running smoothly till week ago. When I am logging into Ubuntu, I got the same message as above described "Failed to initialize HAL". The Problem seems to be, that dbus is not being starting properly or at the right time ???. I checked all syslinks under /etc/rc2.d/ and everything is fine. 
I just saw in the above messages though that others have 'dbus' with starting number 12 
(/etc/rc2.d/S12dbus), but on my laptop it is  50 (/etc/rc2.d/S50dbus).

When I logout and switch to terminal console and run:
'sudo /etc/init.d/dbus start', it says that dbus is being already started.

Running: 
'sudo /etc/ini.d/dbus restart' and then logging in again fixes everything.

Should i change that starting sequence number, but then why now.? It was
starting fine till week ago, and i haven't changed anything under the
system startup levels.

If you need any other information that can help you, just say, because I
have no idea. It's very strange.

-- 
Failed to initalize HAL.
https://launchpad.net/bugs/25931




More information about the desktop-bugs mailing list