GNOME Bugzilla – Bug 690244
Unlock dialog and screen keyboard unresponsive to clicks after D-BUS Lock followed by SimulateUserActivity
Last modified: 2014-08-20 20:24:07 UTC
Created attachment 231612 [details] debug output of locking the screen with unresponsive buttons Running the commands dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock; dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.SimulateUserActivity quite reliably opens an unlock dialog with buttons that can't be clicked. If there is an embedded screen keyboard, it becomes unresponsive to pointer input as well. I can reproduce this on a Nexus 7 ARM device and on a x86_64 desktop. Adding a delay of 1-2 seconds between Lock and SimulateUserActivity seems to make it happen much less frequently. Waiting for the screen to become black again and retrying, brings back pointer input too. Here's the original bug report for Ubuntu on the Nexus 7: https://bugs.launchpad.net/bugs/1088495 Ubuntu 13.04 gnome-screensaver 3.6.1-0ubuntu2
The screen lock is now implemented directly in gnome-shell, not in gnome-screensaver (as it was with older version of GNOME 3 and GNOME 2.x). If the reported problems persists in recent versions of GNOME, please file a new bug against gnome-shell with the "lock-screen" component selected. If your installation is an older version of GNOME that cannot be upgraded (such as an enterprise version), please use the appropriate support mechanism from your vendor, or your distribution instead.