I uploaded a fix to hardy-proposed with attached debdiff. Pending acceptance from Steve now.
** Description changed: 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 + + TEST CASE: + Move /etc/rc2.d/S30gdm to S13gdm to simulate a broken upgrade. Then upgrade to the hardy-proposed version. The symlinks should be fixed to be at level 30 (after hal starts). ** Attachment added: "hardy debdiff" http://launchpadlibrarian.net/14576102/gdm.227838.debdiff -- "Failed to intialize HAL" error message after gdm login. possibly because of wrong gdm priority in /etc/rc*/ https://bugs.launchpad.net/bugs/227838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
