@Matthew, At least bug #855556 seems to have the same core problem. I've published a workaround in bug #855556 that i'm going to copy here, and fix this bug (#861171) and bug #855556.
I think the problem is only related to PolicyKit, because this doesn't handle correctly the 'auth_admin_keep' directive. When an admin user try to halt/restart the system, this directive may ask for admin password an allow only to admin users to halt/restart the system. The workaround goes through modify the 'auth_admin_keep' to 'yes', which allow to any user (admin o desktop user) to halt/restart the system. This is not a full solution, but may be a step forward. -- 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 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
