I'm using Hardy 8.04.2 (originally upgraded from Feisty), with gdm
2.20.7-0ubuntu1.1, and it appears as though I am still affected by this
bug:
ja...@jacob-laptop:~$ ls -l /etc/rc?.d/*dbus
lrwxrwxrwx 1 root root 14 2008-04-29 03:54 /etc/rc1.d/K88dbus - ../init.d/dbus
lrwxrwxrwx 1 root root 14
This also affects kdm - I just had to fix it manually on my laptop's
Kubuntu Hardy x86 install in order to get .fdi files placed into
/etc/hal/fdi/policy/ working.
--
Failed to intialize HAL error message after gdm login. possibly because of
wrong gdm priority in /etc/rc*/
verification done:
- followed the test case moved the old gdm symlink from
/etc/rc2.d/S30gdm to S13gdm to simulate the upgraded, after installed
the proposed package the symlink is moved to S30gdm again, bug is fixed.
** Tags added: verification-done
** Tags removed: verification-needed
--
I can confirm that gdm 2.20.6-0ubuntu2 fixes the problem.
I had the same problem and the update from hardy-proposed moved the
start link and the error message is gone.
--
Failed to intialize HAL error message after gdm login. possibly because of
wrong gdm priority in /etc/rc*/
Accepted into -proposed, please test and give feedback here
** Changed in: gdm (Ubuntu Hardy)
Status: In Progress = Fix Committed
Target: ubuntu-8.04.1 = None
** Tags added: verification-needed
--
Failed to intialize HAL error message after gdm login. possibly because of
wrong
** Changed in: gdm (Ubuntu Hardy)
Target: None = ubuntu-8.04.1
--
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
I'll copy the hardy-proposed version to intrepid once it gets accepted.
** Changed in: gdm (Ubuntu Intrepid)
Status: In Progress = Fix Committed
--
Failed to intialize HAL error message after gdm login. possibly because of
wrong gdm priority in /etc/rc*/
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
I also get the error message(Failed to initialze HAL!) from a fresh
install of Hardy 8.04. cat I moved /etc/rc2.d/24hal to /etc/rc2.d/26.d
after reading the many trouble reports. I am now able to start hal
manually with $ sudo /etc/init.d/dbus start All of the functionality,
(network, etc)
I am running mythbuntu 8.04 and have been regularly applying patches and
rebooting about weekly. I just started getting the Failed to initialize
HAL! error yesterday after patch and reboot, so something changed
recently... I've been running same system/config since Gutsy and have
never seen this
** Changed in: gdm (Ubuntu Intrepid)
Importance: Undecided = High
Assignee: (unassigned) = Martin Pitt (pitti)
Status: Confirmed = In Progress
** Changed in: gdm (Ubuntu Hardy)
Importance: Undecided = High
Assignee: (unassigned) = Martin Pitt (pitti)
Status: New = In
** Attachment added: hal.log
http://launchpadlibrarian.net/14342928/hal.log
--
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
I can confirm this issue. This should be fixed in the postinst script in
the same way Martin Pitt fixed a similar issue in the hal package (cf.
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/25931/)
Thanks,
Dan
--
Failed to intialize HAL error message after gdm login. possibly because of
** Changed in: gdm (Ubuntu)
Status: New = Confirmed
--
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
Desktop Bugs,
14 matches
Mail list logo
