After writing the previous comment I realised we can just have the
behaviour change in the greeter and not in the session if we want.

I think it is better with this solution though because:
- The dialog is more consistent between session and greeter
- The current PolicyKit dialog is bad because cancelling it closes your session 
- i.e. accidentally bumping the power button puts you in a situation where you 
session will close regardless of what you do.
- Shutting down without closing a session is a very destructive operation - it 
is better to encourage the user to close each session manually [*] to avoid 
data loss. Knowledgeable sysadmins can do a forced shutdown by other methods 
and inexperienced users probably know how to power cycle.

mpt/design, can you comment on the above?

I propose we use this solution in raring and just push the greeter
behaviour into SRUs for 12.04, 12.10.

[*] We should probably make it possible to unlock sessions in the
greeter with an administrator password so this is easily possible.

-- 
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

Reply via email to