gdm session may fail if loging in immediately after a boot
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.
Changed in sysvinit: | |
status: | Unconfirmed → Rejected |
Bug # 81670 is a duplicate of this but for Edgy. Marking self as duplicate.