gdm session may fail if loging in immediately after a boot

Bug #84718 reported by C de-Avillez
This bug report is a duplicate of:  Bug #25931: Failed to initalize HAL.. Edit Remove
2
Affects Status Importance Assigned to Milestone
sysvinit (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: initscripts

I am not sure on how to classify this one: gdm, linux-2.6.20, dbus, or initscripts. I decided for initscripts, but I may be wrong.

gdm is started earlier in the boot process, allowing for a login while a series of other init scripts may either be still running or not even started.

This is specially important since dbus and hal are started after gdm -- but a successful login under gdm requires dbus and hal to have already started (S13gdm, and S20dbus).

This is basically a race condition: if the user's craving of the gnome environment is uncontrolled, then the user will login in as soon as the gdm allows.

If dbus/hal have not yet initialised, the resulting session is unusable. The only option is to fall back into a terminal (Ctrl/Alt/F[1-6]), login and restart gdm.

If, otherwise, the user can hold on for a few seconds before logging in, no problems.

I would prioritise this one just below critical, or critical.

Revision history for this message
C de-Avillez (hggdh2) wrote :

Bug # 81670 is a duplicate of this but for Edgy. Marking self as duplicate.

Revision history for this message
Rob Oxspring (roxspring) wrote :

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, although avahi-deamon appears not to be running before the dbus restart, in case thats relevant. I'm running feisty x64 which showing the problem duel booted with edgy x32 which doesn't.

Am I describing a separate problem? any logs / information I can provide that would be useful?

Revision history for this message
C de-Avillez (hggdh2) wrote :

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.

C de-Avillez (hggdh2)
Changed in sysvinit:
status: Unconfirmed → Rejected
Revision history for this message
greymaiden (greymaiden) wrote : Yahoo! Auto Response

Please note: I have changed my e-mail address.

Please forward a copy of your message to <email address hidden> and update your contacts.

This e-mail account is no longer in use and I will not receive your message.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.