After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 690244 - Unlock dialog and screen keyboard unresponsive to clicks after D-BUS Lock followed by SimulateUserActivity
Unlock dialog and screen keyboard unresponsive to clicks after D-BUS Lock fol...
Status: RESOLVED OBSOLETE
Product: gnome-screensaver
Classification: Deprecated
Component: dialog
3.6.x
Other Linux
: Normal major
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2012-12-15 07:33 UTC by marmuta
Modified: 2014-08-20 20:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
debug output of locking the screen with unresponsive buttons (13.47 KB, text/plain)
2012-12-15 07:33 UTC, marmuta
Details

Description marmuta 2012-12-15 07:33:46 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
Comment 1 Bastien Nocera 2014-08-20 20:24:07 UTC
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.