← Back to team overview

dx-packages team mailing list archive

[Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

 

Seems like it is fixed now, in the unity package:

$ sudo apt-cache policy unity
unity:
  Installert: 7.2.2+14.04.20140714-0ubuntu1.1

See changelog: https://launchpad.net/ubuntu/+source/unity/7.2.2+14.04.20140714-0ubuntu1.1
And the associated bug: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349128

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1305586

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, you can't enter your password in the lockscreen.

  [Test case]
  This will work only in the case that your lockscreen is set (from unity control center, lock pane) to lock immediately (when screen turns off).

  1. Open a window that will hold the grab, such as the ssh password dialog or a virtual
     machine (such as virtualbox in fullscreen).
  2. Wait for the lock screen to activate [1].
  3. The screen won't be locked, since it's not possible to steal drag to another window.

  [Regression potential]
  For the same reason of lp:49579, we can't lock the screen (yet) if something takes the grab in X, or we won't able to get input back. This is not a regression because it has never been possible in Ubuntu before, while when we tried that, it caused this bug.

  A possible source of regression might be that we now try to
  grab/ungrab the screen (the only X reliable way for grab checking),
  when showing the dash/hud or the lockscreen itself, and this might
  slow things down a little, but from measurements done this slow down
  is generally about 2ms, so nothing to worry about.

  
  * Compiz Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff *

  [1] You can use this to reduce the locking delay:
        gsettings set org.gnome.desktop.session idle-delay 5
      and resetting it with:
        gsettings reset org.gnome.desktop.session idle-delay

  -----------

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your user session and it be in the same state

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

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


Follow ups