Thank you so much to all the people that moved this bug the last week !!! But I think that most of you are moving in a different direction, and all of the examples in the comments could been solved by the expected behavior commented in post #20 (https://bugs.launchpad.net/ubuntu/+source/unity- greeter/+bug/861171/comments/20):
--- Comment #20 a. Normal user + other users logged: "You just can't turn off the computer because there are more users logged. Please talk to an admin." [ok] (Do nothing) b. Admin user + other users logged: "There are more users logged in the system. Are you sure?" [Yes/No] (Close one by one all logged accounts and shutdown) c. With only 1 user logged (normal or admin) don't ask and shutdown. (Close the session and shutdown) --- Comment #20 end This solution prevent from abnormal session close, hardware shutdown, the actual 'only 1 normal-user logged can't shutdown', normal-user shutdown with multiple active sessions and other situations. Then there was other improvements to this idea, in the following comments. VERY IMPORTANT: Despite about console access and other tricky ways: KIS,S ! -- 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
