Page 1 of 1

unable to click mouse when leaving VM with host key

Posted: 28. Sep 2016, 20:29
by DavidAMS
I have had this problem with at least every version of virtualbox from 5.1.0 to 5.1.6.
My host OS is Ubuntu 16.04. Guest OS doesn't seem to matter, it has happened with both win7 and win10.

The problem is this: When working in the guest OS (with mouse integration enabled), I will press the host key to switch back to the host OS. Then I will switch workspaces (I have a 2x2 grid), and will find that while I can move my mouse cursor, I can't actually click on anything. Most keyboard commands will work still: I can alt+tab around in host OS, and can tab around and type. However in most cases I am unable to open menus (like file, edit, etc).

If I try to switch back to the guest OS, I experience the same problems: I can no longer click the mouse although I can move the cursor.

The only thing that seems to restore mouse usage to normal is to completely stop the VM. If I simply reboot, everything stays the same, but if I fully close that VMs window, my mouse control is returned to normal.

I am also able to get the host+home menu to open, and have tried manually going in and disabling input -> mouse integration. I can see the mouse integration icon in the status bar changing, but it has no effect on my problem.

Oh, I think I have also tried disabling and reenabling the xinput device, which also has no effect. I also have a touch screen, and it doesn't seem to matter if it is a touch from the touchscreen or a mouse click...the problem occurs for either one.

I'm not sure what else to try. I don't see anything in either the virtualbox log or system logs when this happens. It is also a very random problem: it will only happen maybe once every two or three days, and I haven't been able to find a particular behavior that causes it.

Does anyone have any ideas of things I can try the next time this happens?

Re: unable to click mouse when leaving VM with host key

Posted: 28. Sep 2016, 21:03
by socratis
This reminds me vaguely of ticket #15939 which was closed for lack of response from the reporter, despite the interest from the developers. Take a look at it and see if the symptoms match. Oh, the OP reported that downgrading to 5.1.4 fixed it for them.