dx-packages team mailing list archive

[Ara Pulido <ara@xxxxxxxxxx>]

Marking it as Won't Fix in OEM priority project as the behaviour in
Trusty is completely different

** Changed in: oem-priority/precise
       Status: In Progress => Won't Fix

** Changed in: oem-priority
       Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-session in Ubuntu.
Matching subscriptions: dx-packages
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:
  Fix Released
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in “gnome-session” package in Ubuntu:
  Triaged
Status in “indicator-session” package in Ubuntu:
  Triaged
Status in “policykit” package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * A user tries to shut down their machine. They get confused because nothing happens
     when they click shutdown.
   * If someone else is logged in, they will have to ask that person to "Switch User" to
     log in and log out
   * If someone else is logged in and you don't know the password of the account, you
     can't shut down

  [Test Case]

   * Have two login accounts
   * Log both people in, via power cog->lock screen->switch user
   * lock the screen on current account, via power cog->lock screen
   * get back to lightdm via switch user
   * log in to an already logged in account, and try to power off the machine

  [Regression Potential]

   * It wasn't possible to shutdown at all before
   * I can't see a case for a regression, since it never worked to begin with

  [Original Report]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-session/+bug/861171/+subscriptions