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 687940 - Screensaver locks even if virtualbox captures the keyboard, there is no way out
Screensaver locks even if virtualbox captures the keyboard, there is no way out
Status: RESOLVED DUPLICATE of bug 689106
Product: gnome-shell
Classification: Core
Component: lock-screen
3.6.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-11-08 20:48 UTC by Eisenberger Tamás
Modified: 2012-12-02 23:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Eisenberger Tamás 2012-11-08 20:48:37 UTC 
Hy,

Since I've update to gnome 3.6, the new lock screen activates even when the keyboard is captured by virtualbox.

Then when I get back to my machine, the keyboard does not respond to anything. Mouse works, I can slide the lock screen up, but then the password entry is not shown, only the gray background, and I can't even unlock with my fingerprint reader (what works ok normally).

I found no way out except restarting gdm :(

Here's what I've tryed:
- Exit VirtualBox from an other VT using "VBoxManage controlvm VMNAME savestate"
    No change after the VM exited.
- Try to unlock the screen from the VT with "DISPLAY=:0 gnome-screensaver-command --deactivate"
    This worked before 3.6, I used it to remotely unlock my HTPC before starting a movie, anyway now nothing happens..
Comment 1 Hashem Nasarat 2012-11-10 21:12:55 UTC 
As a workaround, in a VT "pkill gnome-shell" and then "DISPLAY=:0 gnome-shell &" should get you back to the desktop.
Comment 2 Eisenberger Tamás 2012-11-10 23:05:17 UTC 
Thanks for the suggestion, I'l try that...
Comment 3 Giovanni Campagna 2012-12-02 23:20:01 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 689106 ***