Bug 1152787 - Mouse cursor is not captured by virt-viewer, gnome-boxes, etc. under GNOME (cursor leaves VM host window when boundary is reached)
Mouse cursor is not captured by virt-viewer, gnome-boxes, etc. under GNOME (c...
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Virtualization:Tools
Other Other
: P5 - None : Normal with 3 votes (vote)
: ---
Assigned To: virt-bugs list
E-mail List
Depends on:
  Show dependency treegraph
Reported: 2019-10-02 13:43 UTC by Marcus Hallett
Modified: 2019-11-26 18:24 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Hallett 2019-10-02 13:43:04 UTC
Occurring on openSUSE Tumbleweed with GNOME 3.32.2 (and 3.34 upon experimentation) and Leap 15.1 with GNOME 3.26.2, virtual machine host windows do not capture the mouse. When the mouse reaches the boundary of the host's window the cursor will not move any further inside the guest. Oftentimes, the cursor will actually leave the window entirely. Adding the "EvTouch USB Graphics Tablet" which enables absolute cursor control (rather than relative) using virt-manager to the machine is only partly helps; though not consistently and effectively. This is also not a correct solution.

This occurs only under GNOME (KDE has it's own problems--looking at you, KDE bug 371877--but this is not one of them). I reproduced it under Leap and Tumbleweed using virt-viewer and gnome-boxes. The same problem cannot be reproduced using Ubuntu 19.04, so I would think this is confined to openSUSE ∴ I am not submitting this to the GNOME bug tracker.
Comment 1 Charles Arnold 2019-10-07 16:53:19 UTC
Could you describe the expected behavior you would like to see with
the mouse pointer in the window running the VM and what should happen
when the attempt is made to move the mouse beyond that window into the
host's screen?

Comment 2 Charles Arnold 2019-11-26 18:24:45 UTC
With spice-vdagent running it has a client mouse mode where there is no need
to grab the mouse by the client, and no mouse lag. This is handled by the
daemon by feeding mouse events into the kernel via uinput. This will only work
if the active X-session is running a spice-vdagent process so that its
resolution can be determined.
It also allows automatic adjustment of the X-session resolution to the client
resolution and supports copy and paste (text and images) between the active
X-session and the client