GNOME Bugzilla – Bug 691094
Unable to unlock screen when virtualbox guest was fullscreen
Last modified: 2013-02-14 20:00:13 UTC
When I leave Win7 in virtualbox fullscreen and gnome's screen lock kicks in, it is impossible to log back in - but I can control both host and vbox guest "blindly" via keyboard without having to authenticate. 1. Win7 is running fullscreen in Virtualbox and has focus 2. Screen lock + blanking due to inactivity timeout 3. Moving the mouse, the standard "Locked" screen appears (key presses do not unblank) 4. Keyboard is not usable, but the blue "Locked" screen can be dragged upwards with the mouse 5. Screen is missing the log-in box, just the top bar and grey background are displayed 6. Now, alt-tab works and displays the "switching" bar, but the desktop remains "hidden" behind the login-box less grey screen. There is full access via keyboard otherwise (alt-tab application screenshots help to see whats going on...). I can even save the vbox with "<host> + q, enter" (for whatever reason however virtualbox fails to load the state saved in that way with an "error unknown") 7. have to switch to another tty and restart gdm Very annoying when you loose unsaved work in the vbox guest... Happens on my laptop as well as on my main PC, both have nearly identical setups. IIRC I sometimes had exactly the same problem but with being asked for the password at point 5 above (could not reproduce now) - here someone describes this issue: https://answers.launchpad.net/ubuntu/+source/gnome-screensaver/+question/217496 system: gdm 3.6.2 linux 3.6.10 systemd 196 x64 lock screen after screen turns off
Created attachment 232677 [details] slave.log
Created attachment 232678 [details] greeter.log
I can confirm similar issue with VmPlayer (5.0.1 build-894247) Win XP (Guest) running. In my case the virtual machine does not have be in full screen. I have tried it locking and unlocking with out VMPlayer and i had no issues. I am not sure if it is related to Video card. I have ati-radeon HD 5450 here is my system configuration: Ubuntu 12.10 GDM 3.6.1 kernel 3.5.0-21-generic x86_64 Dual 30" monitors
Same issue here running Win7 in Virtualbox on Fedora 18: Fedora 18 GDM 3.6.2 Kernel 3.7.2 x86_64 Alienware m11x netbook
I see the same problem as described above. Both at home and at work I have a dual monitor setup. When I run someting in fullscreen on "screen 2" and the application in fullscreen is active when the inactivity lock "kicks in". I am unable to unlock the computer. I cannot use the Esc-key to remove the lock screen, but I can "lift" the lock screen with my mouse. After "lifting" the lock screen with the mouse, there is no "login box". I see the same problem as described above. Both at home and at work I have a dual monitor setup. When I run Citrix/ICA client in fullscreen on "screen 2" and the application in fullscreen is active when the inactivity lock "kicks in". I am unable to unlock the computer. I cannot use the Esc-key to remove the lock screen, but I can "lift" the lock screen with my mouse (exacly as described above). After "lifting" the lock screen with the mouse, there is no "login box". My setup (both at home and at work): Graphic card: Nvidia (With Nvidia kernel module) OS: Ubuntu workstation 12.10 Quantal Quetzal) Gnome version: GNOME Shell 3.6.2 GDM: 3.6.1 CPU: x86_64 My setup (both at home and at work): Graphic card: Nvidia (With Nvidia kernel module) OS: Ubuntu workstation 12.10 Quantal Quetzal) Gnome version: GNOME Shell 3.6.2 GDM: 3.6.1 CPU: x86_64
Is this actually a GDM issue, or a mutter issue? I've experienced the same thing with VNC in fullscreen mode, as well as vmware. With both I've experienced the program being in fullscreen and having the keyboard controls, then the host locked and after unlocking I either couldn't see a login box, or had a login box that vanished, both leaving me at the grey lock screen. Graphics: Intel OS: Gentoo Gnome version: GNOME Shell 3.6.2 GDM: 3.6.2 CPU: x86_64
gnome-shell issue. i believe this is a duplicate of another bug
(In reply to comment #7) > gnome-shell issue. i believe this is a duplicate of another bug Yes, most probably bug 689106. *** This bug has been marked as a duplicate of bug 689106 ***