most mouse clicks not passed through to guest -> no response from reporter

[RandomName123]

Host: OpenSUSE 13.2 64b

Guests: Windows 7, 8.1 & 10

Virtualbox: 5.1.6 r110634 (Qt5.4.2)

Since upgrading from 5.1.4 to 5.1.6, most mouse clicks are not being recognised by guest OS. Mouse cursor movement is OK, and guest OS operation when mouseover guest OS buttons and windows seems correct.

Rough estimate is that maybe 1 in every 10 mouse clicks is recognised by guest.

Problem is also apparent in guest OS menu (created by VirtualBox) - the one for devices, shared folders, etc.. that sits above the guest OS viewport. Trying to use mouse to select anything from this menu mostly fails. But Kwin does respond to window resize, close, etc...

I've reverted back to 5.1.4 so guest systems are now usable.

[Michael Thayer]

Thanks for the report. I have a pretty good idea of which area of the code is causing this problem for you, but I have no idea why. I also have no idea why you are reporting a problem but so far (at least) no one else has. You are probably in the best position to work out what is different about your system. My first guess is something else that also intercepts mouse clicks, but that might very well be completely off.

[RandomName123]

How can I help?

[Michael Thayer]

For a start, you could think about what might be different between your host system and other similar ones, which could cause your one to have this problem and others not. You could also do a bit of on-line searching (Google or the VirtualBox forums for example) to see if other people have had the same thing and if so talk to them to try to find out why.

[RandomName123]

@michael - done that, which is why I'm here. You are clearly of no help. Thank you for your interest.

@anyoneelse - can someone offer some real assistance here, please?

[Michael Thayer]

I don't want to sound like I am lecturing. I think that if you are interested in getting this solved though you will probably want to follow my advice. Of course, I am interested, but there is a definite limit to the amount of time I can justify for it, and trying to guess what is wrong in a problem which is so far only known to affect a single user (who does not seem very interested in working to get it solved) doesn't seem like a promising start.

On the other hand, chances are that someone else will run into this too, so if you just wait it may go away on its own. You could also try posting to the forums<1>, as they are more the place to go for general help.

<1> ​https://forums.virtualbox.org/

[Michael Thayer]

No further response, closing. Anyone who is experiencing this and is interested in investigating should feel free to re-open it though.