*** This bug is a duplicate of bug 25931 ***
** This bug is no longer a duplicate of bug 81670
failed to initialize HAL : gdm init script priority should be at least equal
to dbus one
** This bug has been marked a duplicate of bug 25931
Failed to initalize HAL.
--
gdm session may fail if
*** This bug is a duplicate of bug 81670 ***
** This bug is no longer a duplicate of bug 81670
failed to initialize HAL : gdm init script priority should be at least equal
to dbus one
** Changed in: sysvinit (Ubuntu)
Status: Unconfirmed => Rejected
** This bug has been marked a duplic
*** This bug is a duplicate of bug 81670 ***
Rob, I do not know -- the boot log might show something here.
But, please, let's move to bug # 81670, which is the bug tracking this
issue. Please reply/append the log there.
--
gdm session may fail if loging in immediately after a boot
https://launc
*** This bug is a duplicate of bug 81670 ***
How long should I have to wait after the login prompt before logging in?
I've tried waiting 60s but still get "Failed to initialize hal" dialog.
For what its worth, I find that doing "sudo /etc/init.d/dbus restart"
gets things working again for me, alth
*** This bug is a duplicate of bug 81670 ***
Bug # 81670 is a duplicate of this but for Edgy. Marking self as
duplicate.
** This bug has been marked a duplicate of bug 81670
failed to initialize HAL : gdm init script priority should be at least equal
to dbus one
--
gdm session may fail if l
