shutdown asks for password with only 1 user logged in
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MythTV |
Fix Released
|
Unknown
|
|||
consolekit (Ubuntu) |
Won't Fix
|
Low
|
Unassigned | ||
mythtv (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gdm
from reading similar but not directly related bug reports, I don't know if this gdm or fast-user-switch, so since i'm not actually switching users I'm going with gdm.
system upgraded from jaunty to karmic
power prefs set to ask on power button press
login 1 user
press power button, click shutdown or wait for the timeout
I get a prompt saying other users are logged in and need a password to shutdown.
with this prompt active, I ctrl-alt-f1 and login and run "sudo who". this lists my account on tty1 and tt7, as it should, there are no other users logged in. this was not a problem on jaunty and as I understand it, I should not get this prompt.
ProblemType: Bug
Architecture: i386
Date: Wed Oct 7 21:06:40 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: gdm 2.28.0-0ubuntu14
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: gdm
Uname: Linux 2.6.31-12-generic i686
XsessionErrors:
(gnome-
(gnome-
(polkit-
(nautilus:2919): Eel-CRITICAL **: eel_preferences
(nautilus:3038): Eel-CRITICAL **: eel_preferences
Related branches
- Dave Walker: Approve
-
Diff: 25 lines (+6/-4)1 file modifieddebian/changelog (+6/-4)
Changed in consolekit (Ubuntu): | |
status: | New → Confirmed |
affects: | mythtv (Ubuntu) → consolekit (Ubuntu) |
Changed in mythtv (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in consolekit (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in mythtv: | |
status: | Unknown → New |
Changed in mythtv: | |
status: | New → Fix Released |
Changed in mythtv: | |
status: | Fix Released → Confirmed |
Changed in mythtv: | |
status: | Confirmed → Fix Released |
Thank you for your bug report, could you run ck-list-sessions when getting the issue and copying the log there? It's likely another bug about some cron job registering a session