It's a toss-up: the current behavior is mysterious, but the proposed behavior would be vexatious. Ubuntu would be telling you that the other accounts need to log out, but refusing to offer to do that.
I don't feel strongly about whether it should require admin-only authentication or any-user authentication. The important thing is to have a confirmation step making it clear that forcing logouts of other users is Serious Business. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/861171 Title: Shutdown from greeter does nothing when multiple accounts open Status in The Session Menu: Triaged Status in LightDM GTK+ Greeter: Triaged Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in Unity Greeter: Triaged Status in “gnome-session” package in Ubuntu: Confirmed Status in “indicator-session” package in Ubuntu: Triaged Status in “policykit” package in Ubuntu: Confirmed Status in “unity-greeter” package in Ubuntu: Triaged Bug description: Selecting shutdown from the greeter does nothing when multiple accounts are open. This is because the lightdm user (which the greeter runs as) does not have permission to shutdown while sessions are open. Inside a normal session this would just return you to the login screen. The solution is either for the indicator to say "not allowed" or to run a PolicyKit frontend in the greeter than can get the required permissions to perform the shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/861171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
