Ticket #19043 (new defect)

Opened 6 months ago

Last modified 5 months ago

XWayland breaks mouse behavior on Arch Host

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


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.


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

Change History

Changed 6 months ago by Cortex

Log of Session

comment:1 Changed 6 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 6 months ago by Cortex

Another Addition: Checking 3d acceleration (switching it on) and/or VBoxSVGA mode (with or without 3D acceleration) also brought the error back - even with only 1 monitor.

The problem appears to be complicated...

Last edited 6 months ago by Cortex (previous) (diff)

comment:3 Changed 5 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 5 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 5 months ago by socratis

comment:6 Changed 5 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 5 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 ( changing the title...

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use