Comment 0 for bug 227838

Revision history for this message
Thomas Hammerl (thomas-hammerl) wrote :

Binary package hint: gdm

After upgrades from Feisty to Gutsy and from Gutsy to Hardy I get an error message after logging in with gdm (2.20.5-0ubuntu3) saying "Failed to initialize HAL" but debugging HAL showed that it just comes up fine (see attachment). These are the symlinks to gdm and hal in /etc/rc*:

$ ls -l /etc/rc*/*hal
/etc/rc1.d/K16hal -> ../init.d/hal
/etc/rc2.d/S24hal -> ../init.d/hal
/etc/rc3.d/S24hal -> ../init.d/hal
/etc/rc4.d/S24hal -> ../init.d/hal
/etc/rc5.d/S24hal -> ../init.d/hal
$ ls -l /etc/rc*/*gdm*
/etc/rc0.d/K01gdm -> ../init.d/gdm
/etc/rc1.d/K01gdm -> ../init.d/gdm
/etc/rc2.d/S13gdm -> ../init.d/gdm
/etc/rc3.d/S13gdm -> ../init.d/gdm
/etc/rc4.d/S13gdm -> ../init.d/gdm
/etc/rc5.d/S13gdm -> ../init.d/gdm
/etc/rc6.d/K01gdm -> ../init.d/gdm

HAL is started after gdm and if I login to quickly HAL is not running yet. I was hinted to this by Martin Pitt (who thinks that this an Feisty upgrade issue) in another bug report:

https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/25931/comments/180