VirtualBox

Ticket #19043 (new defect)

Opened 18 months ago

Last modified 11 months ago

XWayland breaks mouse behavior on Linux/Wayland Hosts

Reported by: Cortex Owned by:
Component: other Version: VirtualBox 6.0.14
Keywords: mouse usb clicks Xwayland Cc:
Guest type: other Host type: Linux

Description

On Arch Linux (5.3.7-arch1-1-ARCH), recent as of 2019/10/23 mouse behaviour is broken on a windows 10 host. First mouse click in the guest (on an icon, however not at the background image) introduces this behaviour. Afterwards mouse clicks in guest and host system are not properly recognized anymore (on guest, GNOME seams to work correctly, however firefox, chromium, VirtualBox Manager and others don't). Keyboard function is correct. As soon as the guest is powered off, mouse behaviour is normal in the host.

Changing mouse settings from PS/2 to tablet mode does not change the behaviour.

I could track the error down to the upgrade of usbutils-010 to usbutils-012. Downgrading usbutils to 010 solved the error

The log of the session is attached.

Attachments

Windows10-2019-10-23-09-48-58.log Download (137.8 KB) - added by Cortex 18 months ago.
Log of Session

Change History

Changed 18 months ago by Cortex

Log of Session

comment:1 Changed 18 months ago by Cortex

Just to add: the problem re-appears (despit having usbutils-010) installed when the host is configured to 2 monitors. No matter whether 2d & 3d hardware acceleration are used and in Both VGA and SVGA mode.

comment:2 Changed 18 months ago by Cortex

Another Addition: Checking 3d acceleration (switching it on) also brought the error back - even with only 1 monitor.

Version 0, edited 18 months ago by Cortex (next)

comment:3 Changed 18 months ago by Cortex

Even after the downgrade of usbutils the problem re-occured after some time (1-2 h). In turn it had again been constantly present. Overall the occurrence of the problem seems highly erratic to me.

comment:4 Changed 17 months ago by Cortex

Ok, finally I could track the problem down. Deactivating Wayland leads to expected behaviour.

So there is a problem with the interaction between VirtualBox and xwayland.

comment:5 Changed 17 months ago by socratis

comment:6 Changed 17 months ago by socratis

So, should I change the title from "usbutils 012 breaks mouse on Linux" to something like "xwayland breaks mouse behavior" or something similar?

If you could edit the ticket's title, what would you change it to?

comment:7 Changed 17 months ago by socratis

  • Component changed from USB to other
  • Summary changed from usbutils 012 breaks mouse on Linux to XWayland breaks mouse behavior on Arch Host

Based on the discussion in the forums ( https://forums.virtualbox.org/viewtopic.php?f=7&t=95290#p463227) changing the title...

comment:8 Changed 11 months ago by mmikk

The issue still exists in 6.1.6 @ Wayland Ubuntu 20.04.

Until guests tools are started on guest OS (Windows 10) everything works fine. But after some operations (for example starting firefox with some sites - I could not track which yet) mouse clicks are lost in BOTH the guest OS and the host OS (the cursor image in the host OS is frozen to the shape of Guest OS cursor image). The issue remains until Guest OS is turned off.

When switched from Wayland to X11 the issue does not occur.

comment:9 Changed 11 months ago by mmikk

Also please update the title to: ...mouse behavior on Linux/Wayland Host - as multiple distros are affected and multiple versions of the virtual box have the issue unfixed.

comment:10 Changed 11 months ago by fbatschu

  • Keywords Xwayland added
  • Summary changed from XWayland breaks mouse behavior on Arch Host to XWayland breaks mouse behavior on Linux/Wayland Hosts

comment:11 Changed 11 months ago by mmikk

Are there some actions I could do that could help diagnose where the issue comes from? Please also update the version of the Virtual Box to 6.1.6 as this issue reproduces in this version.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use