fails to restart (not running) gdm on maverick->natty upgrade
Bug #745532 reported by
Michael Vogt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pam (Ubuntu) |
Fix Released
|
Low
|
Stéphane Graber | ||
Natty |
Fix Released
|
Low
|
Stéphane Graber | ||
Oneiric |
Invalid
|
Undecided
|
Unassigned |
Bug Description
During a maverick->natty upgrade I got a debconf prompt about having to manually restart gdm. During the upgrade gdm was not running. This is a pretty unusual situation so not a big deal and mostly cosmetic (and the upgrade did not fail or anything).
Attached a screenshot from the VM.
Related branches
tags: | added: iso-testing |
Changed in pam (Ubuntu Natty): | |
assignee: | nobody → Stéphane Graber (stgraber) |
Changed in pam (Ubuntu Natty): | |
status: | Triaged → Fix Committed |
Changed in pam (Ubuntu Oneiric): | |
status: | New → Invalid |
tags: | added: patch |
To post a comment you must log in.
yes, gdm is handled specially in the service restarting; we call 'reload' instead of 'restart', since this is how we signal gdm to reload libraries without crashing currently open sessions. So if the service isn't running, 'reload' fails; we should fix the script to check for a running service first.