unlock keystrokes sent to virtual-box session

Bug #1311036 reported by Mark Petryk
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Unity
New
Undecided
Unassigned

Bug Description

When Virtual-Box is running a Windows session full screen and the nix host locks the screen, no keyboard is being sent to the unlock screen, but is being sent to the Virtual-Box session instead. This can be verified by remoting in to the Windows machine with another box and watching a text-input such as notepad as the user tries to unlock the nix host. The only resolution is to remote in to the Windows session and shut it down at which point the keyboard is directed to the nix unlock screen properly and the machine can be unlocked. It is also possible to switch to a desktop that does not have the full-screen Windows session, but a regular nix desktop and when the screen locks there is no problem unlocking it. This is unique to the recent "Ubuntu 14.04 LTS" upgrade - it did not occur in 13.10.

Revision history for this message
Simon Steinbeiß (ochosi) wrote :

Are you sure this bug is with light-locker?

By default, Unity/Ubuntu doesn't use light-locker but instead comes with a built-in locker and the problem you're describing sounds similar to a known issue with it.
(For reference: https://bugs.launchpad.net/bugs/1305586)

Revision history for this message
Mark Petryk (mcrk) wrote : Re: [Bug 1311036] Re: unlock keystrokes sent to virtual-box session

No, sir, I am not ~certain~ this is a problem with light-locker, but I
was directed to post a bug by a canonical developer. How can I query?

The machine does respond to ctrl-alt-F1 where I can log in and 'ps aux'
for running tasks and so on.

Happy to help, but I need some guidance.

~mark
~c:469-556-5075
~t:<email address hidden>
~w:http://www.lorimarksolutions.com

On 04/23/2014 04:08 AM, Simon Steinbeiß wrote:
> Are you sure this bug is with light-locker?
>
> By default, Unity/Ubuntu doesn't use light-locker but instead comes with a built-in locker and the problem you're describing sounds similar to a known issue with it.
> (For reference: https://bugs.launchpad.net/bugs/1305586)
>

Revision history for this message
Simon Steinbeiß (ochosi) wrote :

So you installed and set up light-locker yourself in 14.04? If you're using a default install, I'm rather certain that it's not light-locker you're using.

You can easily query whether it is running in the terminal "ps -A | grep light-locker" or by checking whether the package is installed in software center.

Revision history for this message
Mark Petryk (mcrk) wrote :

I did not do anything than a normal upgrade from 13.10 to 14.04.
Light-Locker is not installed at this time according to software center.

If you wouldn't mind directing me to how to determine which locker is
running, I'll pursue that.

Thank you.

~mark
~c:469-556-5075
~t:<email address hidden>
~w:http://www.lorimarksolutions.com

On 4/23/2014 5:59 AM, Simon Steinbeiß wrote:
> So you installed and set up light-locker yourself in 14.04? If you're
> using a default install, I'm rather certain that it's not light-locker
> you're using.
>
> You can easily query whether it is running in the terminal "ps -A | grep
> light-locker" or by checking whether the package is installed in
> software center.
>

Revision history for this message
Simon Steinbeiß (ochosi) wrote :

If light-locker isn't installed, it's certainly not in use ;)
Assigning this bug to unity instead.

affects: light-locker (Ubuntu) → ubuntu
affects: ubuntu → unity
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.