Comments on: Ubuntu 6.10 Annoyance: `failed to initialize HAL` error http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/ "The time has come...to talk of many [technologies]." --Lewis Carroll('The Walrus and the Carpenter') Fri, 05 Dec 2008 03:02:55 +0000 http://wordpress.org/?v=2.6.5 By: HAL | Garrotter blogja http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-137432 HAL | Garrotter blogja Sat, 15 Nov 2008 12:15:16 +0000 http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-137432 [...] megoldás innen származik. Köszönet érte. Ha tetszett, oszd meg ezt a bejegyzést [...] [...] megoldás innen származik. Köszönet érte. Ha tetszett, oszd meg ezt a bejegyzést [...]

]]> By: gene kemp http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-137050 gene kemp Tue, 08 Apr 2008 00:30:01 +0000 http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-137050 thanks for the info. Needed to boot windows xp first on a dual boot machine with a very inexperienced user that couldn't handle the boot screen. Made a change from default 0 to default 8, xp being the 8th line on the list, using sudo gedit /boot/grub/menu.lst This moved the highlighted selection bar to xp to boot first. Then upon rebooting and selecting ubuntu the hal problem appeared. Using your time delay suggestion worked thank you thanks for the info. Needed to boot windows xp first on a dual boot machine with a very inexperienced user that couldn’t handle the boot screen. Made a change from default 0 to default 8, xp being the 8th line on the list, using sudo gedit /boot/grub/menu.lst This moved the highlighted selection bar to xp to boot first. Then upon rebooting and selecting ubuntu the hal problem appeared. Using your time delay suggestion worked thank you

]]> By: Matthew Painter http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-133529 Matthew Painter Fri, 26 Oct 2007 13:04:53 +0000 http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-133529 If you want to debug: sudo hald --daemon=no --verbose=yes My HAL wouldn't start after upgrading to 6.10 because a file was in the wrong place: cd /var/cache/hald sudo mv fdi-cache~ fdi-cache If you want to debug:

sudo hald –daemon=no –verbose=yes

My HAL wouldn’t start after upgrading to 6.10 because a file was in the wrong place:

cd /var/cache/hald
sudo mv fdi-cache~ fdi-cache

]]> By: tabrez http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-90661 tabrez Thu, 26 Jul 2007 07:41:40 +0000 http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-90661 Another fix at blog.ubrio.us: <a href="http://blog.ubrio.us/gnome/ubuntu-error-hal-failed-to-initialize-udev-address-already-in-use-solution/" rel="nofollow">udev address already in use</a> Another fix at blog.ubrio.us:
udev address already in use

]]> By: hggdh http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-43928 hggdh Thu, 19 Apr 2007 13:06:40 +0000 http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-43928 I stand corrected :-) On my defence, I have never used autologins because of the huge security risk (since I float around different customers, having my laptop autologin is an invitation to be had; YMMV). Anyway, delaying autologin is not a solution, but a bypass. For full resolution, change /etc/rc[2345].d/S20dbus to /etc/rc[2345].d/S12dbus (this is how it is on Feisty; I do not use Edgy): sudo mv /etc/rc2.d/S20dbus /etc/rc2.d/S12dbus sudo mv /etc/rc3.d/S20dbus /etc/rc3.d/S12dbus sudo mv /etc/rc4.d/S20dbus /etc/rc4.d/S12dbus sudo mv /etc/rc5.d/S20dbus /etc/rc5.d/S12dbus What will happen: it will take slightly longer for the autologin to complete, but you will not have this issue anymore. In fact, the time needed to initialise dbus will vary depending on your hardware. It can be as low as some few seconds, and as high as some tens of seconds. In my case, due to another issue (apparently resolved by HAL 0.5.9) it takes about 30 seconds for my LVM partitions to be available. I stand corrected :-)

On my defence, I have never used autologins because of the huge security risk (since I float around different customers, having my laptop autologin is an invitation to be had; YMMV).

Anyway, delaying autologin is not a solution, but a bypass.

For full resolution, change /etc/rc[2345].d/S20dbus to /etc/rc[2345].d/S12dbus (this is how it is on Feisty; I do not use Edgy):

sudo mv /etc/rc2.d/S20dbus /etc/rc2.d/S12dbus
sudo mv /etc/rc3.d/S20dbus /etc/rc3.d/S12dbus
sudo mv /etc/rc4.d/S20dbus /etc/rc4.d/S12dbus
sudo mv /etc/rc5.d/S20dbus /etc/rc5.d/S12dbus

What will happen: it will take slightly longer for the autologin to complete, but you will not have this issue anymore.

In fact, the time needed to initialise dbus will vary depending on your hardware. It can be as low as some few seconds, and as high as some tens of seconds. In my case, due to another issue (apparently resolved by HAL 0.5.9) it takes about 30 seconds for my LVM partitions to be available.

]]> By: Dave http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-43924 Dave Thu, 19 Apr 2007 12:40:14 +0000 http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-43924 >> "How do you make the Autologin have a 5 second Delay before automatically logging in?" > "You do not. There is no such option, unless you go and hack in." Sure there is! System > Administration > Login (or sudo gdmsetup) > Security > Timed Login. I use a 15 second delay. (Or perhaps instead hggdh could actually explain which files need changing to change the startup priority as they suggest? Because I would only be guessing.) >> “How do you make the Autologin have a 5 second Delay before automatically logging in?”

> “You do not. There is no such option, unless you go and hack in.”

Sure there is! System > Administration > Login (or sudo gdmsetup) > Security > Timed Login. I use a 15 second delay.

(Or perhaps instead hggdh could actually explain which files need changing to change the startup priority as they suggest? Because I would only be guessing.)

]]> By: hggdh http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-43922 hggdh Thu, 19 Apr 2007 12:17:53 +0000 http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-43922 You do not. There is no such option, unless you go and hack in. The best option is to change the startup priority of dbus, so that it will start before gdm/kdm/whateverdm. On Feisty this has been done, but I do not know if it (will be|has been) backported to Edgy. This is a rather simple change. You do not. There is no such option, unless you go and hack in.

The best option is to change the startup priority of dbus, so that it will start before gdm/kdm/whateverdm. On Feisty this has been done, but I do not know if it (will be|has been) backported to Edgy. This is a rather simple change.

]]> By: tenka http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-43869 tenka Thu, 19 Apr 2007 01:07:25 +0000 http://beans.seartipy.com/2006/11/25/ubuntu-610-annoyance-failed-to-initialize-hal-error/#comment-43869 How do you make the Autologin have a 5 second Delay before automatically logging in? How do you make the Autologin have a 5 second Delay before automatically logging in?

]]>