STEPS TO REPRODUCE 1. Start a VM in Virtualbox (tested with Windows 11) 2. Try to click on something 3. OBSERVED RESULT Virtualbox app window works normally only until a VM is started after that mouse input no longer works EXPECTED RESULT Clicks are received by the VM and the app and do appropriate actions. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.84 Qt Version: 5.15.2 ADDITIONAL INFORMATION On wayland
Duplicate of Bug 427060?
The report above describes an issue where a Linux guest gets misplaced mouse input from a Windows host. My issue is that Oracle virtualbox app stops responding to any mouse input after a VM (with Windows in this case) starts. So, no I wouldn't say it's a duplicate.
Could you add more detail? I run Neon on VB quite often and didn't see such problems. So the input doesn't work inside guest OS?
I do these following steps: 1. I start Oracle VM Virtualbox Manager 2. I start my Windows 11 VM 3. I click inside the VM window From now on, there is no cursor when I am inside the VM window, clicking blindly doesn't do anything, clicking inside Virtualbox Manager doesn't do anything. If I close the VM, Virtualbox Manager starts responding to mouse clicks.
And just now I also noticed this only happens when the VM starts in full-screen mode or is switched into full-screen mode. Otherwise everything works correctly. Also while running in full-screen mode it's impossible to activate the top/bottom toolbar after it was hidden at least once before. I will try to find out more about that.
So I suppose you are complaining about no input in guest OS, otherwise I assume you are aware of Host key (right Ctrl by default) to ungrab the input. I can't test it on Windows, could you test on Linux host OS? Also, what guest OS do you use, did you try Neon iso? Also, if guest OS you run is installed (to VM internal disk), you could try to install VirtualBox Guest Additions there.
(In reply to Andrey from comment #6) > So I suppose you are complaining about no input in guest OS, otherwise I > assume you are aware of Host key (right Ctrl by default) to ungrab the input. > > I can't test it on Windows, could you test on Linux host OS? > Also, what guest OS do you use, did you try Neon iso? > Also, if guest OS you run is installed (to VM internal disk), you could try > to install VirtualBox Guest Additions there. I am using a Linux host, Arch Linux + Kde Plasma. Windows 11 is installed as my guest OS. I do have Guest Additions installed and working correctly. I will try using Linux on Linux though. I know how Host key in VMs is supposed to work and everything works correctly in Plasma Xorg session, it's just the Wayland one that is broken. It's like when mouse control is taken from the host and given to the guest it gets lost somewhere in between and neither work.
I also tried to run Arch Linux Host and KDE neon user as Guest. After I click and release in the VM window once, mouse input stops working, host key stops working and Virtualbox manager app also stops responding to mouse input. Closing the VM restores mouse functionality in the Virtualbox manager app.
I'm not sure if we could do anything without a way to reproduce. What is your Graphic card, can you try on Intel? What is you VirtualBox version? Please try to update if it's not latest. The same for your host OS. Can you find other people with this issue?
(In reply to Andrey from comment #9) > I'm not sure if we could do anything without a way to reproduce. Can you not reproduce with steps in Comment #4 ? > What is your Graphic card, can you try on Intel? AMD Vega 8, I can try a different PC or the same one with a different distro. > What is you VirtualBox version? Please try to update if it's not latest. > The same for your host OS. 6.1.26, the latest one. All other packages are up-to-date as well. > Can you find other people with this issue? Hopefully someone will find this report and confirm this issue, otherwise I have no way of finding anyone.
I don't have problems on Intel graphics. It might be your issue is AMD specific, better try on Intel then.
(In reply to Andrey from comment #11) > I don't have problems on Intel graphics. > It might be your issue is AMD specific, better try on Intel then. I just tried the same thing on a different PC. It has Manjaro as host and my guest OS was KDE Neon. Hardware is intel CPU + GPU and it has the exact same issue. Next I will try a different (older) version of Virtualbox and I a different distro.
Did you do some unusual pointer configurations maybe in the VM? Also maybe worth trying different VMs.
(In reply to Andrey from comment #13) > Did you do some unusual pointer configurations maybe in the VM? No, I use stock config only, nothing special. > Also maybe worth trying different VMs. Sure, I can try gnome-boxes and vmware.
I'm seeing the same with VirtualBox 6.1.34 on OpenSUSE Tumbleweed (Thinkpad X1 Yoga 3rd, Intel graphics).
This seems to be about an application bug; if you still have this problem, please report it to Oracle.