Ernst, If you follow the comments you'll figure out that some time the computer should shut down and some time it shouldn't, depending on the user requesting the shut down and the amount of users logged in.
After some comments, we're proposing some ideas of how it could be shown or communicated to the user / admin that is requesting the action. The examples of my last comment has to be connected with the others examples of previous comments, then having this result, for instance: "You, Florian, ethanay, daniel, Lionel and 3 more are logged." "You just can't turn off the computer because there are more users logged. Please talk to an admin." [ok] (this is the case where a user request a shut down when the are 8 people logged in) --- Anyway, the case you say in your comment has been commented before, and the main idea is that your wife will be able to shut down the system in the following cases: - She is an admin - She is an user and is the only one logged in the computer --- Your proposal related to org.freedesktop.consolekit.system.stop- multiple-users, as far as I know, allow to any user to shut down the system (please correct me if I'm wrong). This solution was discussed as a preliminary workaround, until this bug had been corrected properly. -- 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 : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
