Greeter indicates session is logged into after logout

[Sebastien Bacher]

Using saucy, users stay marked as logged-in after their logout

To reproduce:
1. Boot to Unity Greeter
2. Log into a session
3. Log out

Expected result:
Last logged in user is selected and not marked as logged in. (has > to the left of the name)
Observed result:
Last logged in user is selected and is marked as logged in.

Regression potential:
Low. Fixed invalid ordering of arguments in a signal handler, code was invalid before.

[Robert Ancell (robert-ancell)]

This is not a logind issue - the greeter gets the session list from the daemon. The daemon is removing the session from the list but the greeter is not picking this up for some reason. The bug is either in liblightdm-gobject or unity-greeter.

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:lightdm at revision 1828, scheduled for release in lightdm, milestone Unknown

[Launchpad Janitor (janitor)]

This bug was fixed in the package lightdm - 1.9.1-0ubuntu1

---------------
lightdm (1.9.1-0ubuntu1) trusty; urgency=low

  * New upstream release:
    - Correctly set $XDG_SESSION_CLASS for greeters. This was regressed in 1.7.5
      for ConsoleKit and was never passed to logind. logind/ConsoleKit treat
      greeter sessions without this set as user sessions. This causes greeters
      to show the lightdm user able to be logged in with.
      (LP: #1242939)
    - Set $USER when running the session-setup-script. This is a regression from
      1.7.5. (LP: #1245957)
    - Fix notification of sessions being logged out. This is a regression from
      1.7.5 and caused greeters to show sessions logged in after they had been
      logged out. (LP: #1245295)
    - Refactor liblightdm user scanning to be simpler and more reliable. This
      fixes bugs where some properties wouldn't be updated when they changed in
      accounts service.
    - Add support for a "display-stopped-script" field in lightdm.conf. The
      "display-stopped-script" field allows us to run a script right after
      stopping the display server.
    - Allow dm-tool to run outside of a session if it doesn't need to be.
    - Set $MIR_SERVER_NAME to assign a name to launched sessions. Also use a
      "greeter-" prefix for greeter sessions for the benefit of
      unity-system-compositor.
 -- Robert Ancell <email address hidden> Wed, 30 Oct 2013 14:11:16 -0700

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Launchpad Janitor (janitor)]

This bug was fixed in the package lightdm - 1.8.4-0ubuntu1

---------------
lightdm (1.8.4-0ubuntu1) saucy-security; urgency=low

  [ Marc Deslauriers ]
  * SECURITY UPDATE: improper guest account confinement (LP: #1243339)
    - CVE-2013-4459

  [ Robert Ancell ]
  * New upstream release:
    - Implement missing guest-wrapper functionality and enable it for Ubuntu.
    - Update AppArmor scripts to work in Ubuntu 13.10. (LP: #1243339)
  * debian/50-guest-wrapper.conf:
    - Configure guest session wrapper to use

lightdm (1.8.3-0ubuntu1) saucy; urgency=low

  * New upstream release:
    - Correctly set $XDG_SESSION_CLASS for greeters. This was regressed in 1.7.5
      for ConsoleKit and was never passed to logind. logind/ConsoleKit treat
      greeter sessions without this set as user sessions. This causes greeters
      to show the lightdm user able to be logged in with.
      (LP: #1242939)
    - Set $USER when running the session-setup-script. This is a regression from
      1.7.5. (LP: #1245957)
    - Fix notification of sessions being logged out. This is a regression from
      1.7.5 and caused greeters to show sessions logged in after they had been
      logged out. (LP: #1245295)
 -- Marc Deslauriers <email address hidden> Mon, 04 Nov 2013 13:35:26 -0500