14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with VirtualBox VMs Running

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1322769/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

Thank you Brian. For the life of me I couldn't sort out the interface as
its the first report I have done and its all a bit intimidating for first
time users of the report system.
On 28/05/2014 4:45 am, "Brian Murray" <email address hidden> wrote:

> ** Package changed: ubuntu => unity (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1322769
>
> Title:
> 14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with
> VirtualBox VMs Running
>
> Status in “unity” package in Ubuntu:
> New
>
> Bug description:
> I have replicated this bug on two different laptops, one at work
> running mulitple monitors, one at home running a single monitor.
>
> Symptom: When the Unity System Settings Lock Screen Settings activate,
> and I notice the screen has gone blank and locked, I re-activate the
> keyboard (usually left CRTL) and the 14.04 LTS Login Screen appears.
>
> In all cases the keyboard is locked out and non-responsive, I can
> click on the password box for my account and anything I type no longer
> appears. I have to select "Switch Account" option with the mouse to
> get a new login screen for my account and I can log in.
>
> In some cases both the keyboard and the mouse input is locked out and
> non-responsive. I can not select "Switch Account" and must power off
> the laptop which of course is dangerous for the file systems of both
> Windows VMs that are running and the host/14.04 LTS file system. I
> have already corrupted the Windows VM file systems and had to repair
> while testing this bug for repeatability.
>
> Both laptops run the AMD64 version of Ubuntu 14.04 LTS.
> Both have built in Intel Integrated Graphics, one laptop with the older
> Ironlake, one with the newer ivy bridge.
>
> Both are running Oracle VirtualBox but different version:
>
> 1. Home is running the Ubuntu 14.04 Repository version of Oracle
> VirtualBox (Currently 4.3.10_Ubuntu r93012)
> 2. Work is running the Oracle downloadable AMD64 version of Oracle
> VirtualBox Currently 4.3.12
> 3. Both have the respective Oracle Virtual Box Extensions installed for
> 4.3.10 and 4.3.12
> 3. Both are running Windows 7 64 VMs
>
> Both 14.04 LTS have the following System Settings for Lock Screen:
> Brightness slider - All the way left
> Dim screen to save power - Checked
> Lock - Switch to ON position
> Lock Screen after: 5 minutes
> Require my password when weking form suspend - Checked
>
>
> I have tested this with both a VM running (no other running applications
> were tested) and with no apps running (fresh boot and login into 14.04 LTS
> unity desktops).
>
> 1. On fresh boot with no apps running the lock screen activates (after
> 5 min of no activity) and when I re-activate the laptops (usually
> pressing left CTRL on keyboard) I get the login screen and can enter
> my password successfully and the Unity desktop is presented.
>
> 2. On fresh boot with a Windows 7 VM running the lock screen activates
> (after 5 min of no activity) and when I re-activate the laptops
> (usually pressing the left CTRL on the keyboard) ...

This looks similar to this bug: https://bugs.launchpad.net/unity/+bug/1305586

However - I've found that another issue is that whatever application has held on to the cursor, you will end up typing your password directly into. Google Chrome and Chromium seem to be the two most popular culprits.