desktop-packages team mailing list archive

[Robert Ancell <robert.ancell@xxxxxxxxxxxxx>]

** Changed in: lightdm
       Status: Fix Committed => Fix Released

** Changed in: lightdm (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371378

Title:
  Session locking doesn't work if the session was unlocked after
  changing VT

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Triaged
Status in lightdm package in Ubuntu:
  New

Bug description:
  Test machine: Ubuntu 14.04 with lightdm-1.10.1-0ubuntu1 and lightdm
  trunk revision 2064

  Reproducing the bug:

  1. Log into an user session using Unity, Gnome 3 or Cairo-Dock session.
  2. If using a Gnome 3 session, trigger the screensaver by executing "xdg-screensaver lock", and then unlock it by entering the user password (this is needed to avoid bug #1371374).
  3. Lock the session executing "dm-tool lock" in a terminal.
  4. A new greeter is displayed.
  5. Switch to the user session by switching VT (e.g. Alt+Ctrl-F7).
  6. The user session is locked by the screensaver (which under a Unity session just looks like the greeter), prompting for the user password.
  7. Unlock the screensaver by introducing the user password.
  8. Lock the session again ("dm-tool lock").
  9. The greeter is shown again.
  10. Switch to the user session by switching VT (e.g. Alt+Ctrl-F7).
  11. The session isn't locked at all.

  Causes:

  Lightdm is not aware of VT changes, therefore when the session is
  unlocked by using the screensaver in the user session's VT instead of
  the greeter, lightdm is thinking that the active session is still the
  greeter session.

  When locking the session afterwards, in the function
  seat_set_active_session() the session to be activated (the greeter) is
  compared to the session that light thinks that is active, which it
  thinks is the greeter because it was the last session activated by
  lightdm, and therefore locking is not performed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1371378/+subscriptions