Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1528200 - cursor not initially visible in virt-manager/gnome-boxes window
Summary: cursor not initially visible in virt-manager/gnome-boxes window
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: spice-gtk
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marc-Andre Lureau
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1585680 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-21 09:39 UTC by Edvard
Modified: 2019-03-29 19:10 UTC (History)
20 users (show)

Fixed In Version: spice-gtk-0.36-4.fc30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-29 19:10:48 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Example of UI glitch (959.36 KB, image/png)
2018-02-27 21:33 UTC, Edvard 		no flags Details
virt-manager --debug output (38.52 KB, text/plain)
2018-10-25 02:34 UTC, Jordan Pisaniello 		no flags Details
View All

Description Edvard 2017-12-21 09:39:50 UTC 
Description of problem:


Version-Release number of selected component (if applicable): 1.4.3


Steps to Reproduce:
1. Log into a Wayland session
2. Start a Virtual machine and capture mouse input
3. After a while you'll notice that the mouse cursor completely disappears from the VM including the virt-manager GUI.

Actual results:
Mouse cursor is invisible and virt-manager window management is buggy.


Expected results:
Mouse cursor should always be visible when capture in a VM and when interacting with the virt-manager GUI.


Additional info:
I've noticed this on both Fedora 26 and Fedora 27 when running Wayland. This problem does not occur when using Xorg however. Everything will work fine to begin with but after a short period of time, typically after escaping from the VM for a bit and then returning to it the mouse cursor will be invisible when captured in the VM, and trying to escape and then interact with the virt-manager GUI also results in an invisible mouse cursor. The cursor is still there as I can still click UI elements but the cursor icon itself is gone.
Comment 1 Edvard 2018-02-24 19:26:13 UTC 
Update: This is still an issue and it's currently rendering virt-manager unusable for me on Wayland.
Comment 2 tw-bugs-redhat 2018-02-24 19:30:33 UTC 
I've been working around it by moving the mouse cursor off the window so it is visible, then carefully maneuvering the mouse to any of virt-manager's menus and clicking it. When you click on a menu (if you can make it there with the cursor invisible), the cursor reappears. I have to use a Tablet device with every VM to avoid this as a constant issue, but it still happens frequently.
Comment 3 Edvard 2018-02-27 21:33:51 UTC 
Created attachment 1401535 [details]
Example of UI glitch

Notice how the VM is in "full screen" mode yet the alignment is completely off. In this example it's impossible to interact with the Windows 10 start menu as it's completely off screen.
Comment 4 tgvita 2018-07-21 02:31:56 UTC 
same symptom even in F28, In X session it won't occur, in Wayland session it does. I think the upstream should handle this.
Comment 5 tgvita 2018-07-21 02:36:44 UTC 
(In reply to tw-bugs-redhat from comment #2)
> I've been working around it by moving the mouse cursor off the window so it
> is visible, then carefully maneuvering the mouse to any of virt-manager's
> menus and clicking it. When you click on a menu (if you can make it there
> with the cursor invisible), the cursor reappears. I have to use a Tablet
> device with every VM to avoid this as a constant issue, but it still happens
> frequently.

yup, clicking on the "exit fullscreen" button on that small slide-down top bar is way too hard, drag on the window (i mean top bar) with invisible cursor will make the cursor it visible, but that means you never enter the fullscreen mode.
Comment 6 Cole Robinson 2018-08-05 22:08:36 UTC 
What VM OS is everyone running?
Is everyone's VMs using spice? qxl video device? Does switching to VNC and/or VGA video device make the issue go away?

Can someone run virt-manager --debug from a terminal, reproduce the issue, and attach the full console output? Maybe
Comment 7 Cole Robinson 2018-10-09 14:39:17 UTC 
tgvita are you still reproducing with latest f28 packages? If so, please provide the info requested in comment #6
Comment 8 Jordan Pisaniello 2018-10-25 02:32:50 UTC 
(In reply to Cole Robinson from comment #7)
> tgvita are you still reproducing with latest f28 packages? If so, please
> provide the info requested in comment #6
Not the individual you were questioning, but I'm experiencing the same issue described here.

> What VM OS is everyone running?
I have been using the latest 'everything' ISO of CentOS 7. This happens before I actually even install. As soon as I launch the VM and try to navigate out of its screen, the cursor is gone within all the other UI elements of virt-manager (moving the cursor back out to the desktop works as expected).

>Is everyone's VMs using spice? qxl video device? Does switching to VNC and/or VGA video device make the issue go away?
Not sure about this, but could definitely find out some more information after some reading about this.

>Can someone run virt-manager --debug from a terminal, reproduce the issue, and attach the full console output?
Sure, I'll attach my output after I save this comment. Some lines of interest may be:

934: (virt-manager:25017): Gdk-CRITICAL **: 22:23:06.370: gdk_wayland_window_handle_configure_popup: assertion 'impl->transient_for' failed
952: (virt-manager:25017): GSpice-CRITICAL **: 22:23:34.677: spice_gtk_session_request_auto_usbredir: assertion 's->auto_usbredir_reqs > 0' failed

Please let me know if there is any other information I could gather and provide for you.
Comment 9 Jordan Pisaniello 2018-10-25 02:34:07 UTC 
Created attachment 1497258 [details]
virt-manager --debug output
Comment 10 Jordan Pisaniello 2018-10-25 19:08:15 UTC 
It also might be worth noting that something similar also seems to happen with gnome-boxes as well. See: https://bugzilla.redhat.com/show_bug.cgi?id=1585680
Comment 11 Cole Robinson 2018-11-12 13:48:08 UTC 
If this affects gnome-boxes too, it's probably not virt-manager specific. Moving to spice-gtk for futher triage.

In the past similar issues actually need kernel qxl fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1200901

So the interesting bits to confirm are: what VM OS is everyone using (already heard this affects centos), and does switching the VM to use plain VGA instead of QXL make any difference
Comment 12 Cole Robinson 2018-11-12 13:48:26 UTC 
*** Bug 1585680 has been marked as a duplicate of this bug. ***
Comment 13 Grzegorz Witkowski 2018-12-15 01:26:28 UTC 
The same problem in F29 host, running VMs: F28 (workstation), F29 (server/text), Win10 with all updates. 
kernel 4.19.8-300.fc29.x86_64
xorg-x11-server-Xwayland-1.20.3-1.fc29.x86_64
spice-gtk3-0.35-3.fc29.x86_64
spice-server-0.14.0-5.fc29.x86_64
spice-vdagent-0.18.0-2.fc29.x86_64
spice-glib-0.35-3.fc29.x86_64
qemu-kvm-3.0.0-2.fc29.x86_64
libvirt-daemon-kvm-4.7.0-1.fc29.x86_64
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

I tried changing the QXL to virtio. Changing the resize/autoresize, scale display settings. Still the same issue.
Someone online suggested adding EvTouch USB Graphics Tablet. That seem to improved it slightly in Win10 case with QXL.
Because of this issue virt-manager is currently unusable.
Comment 14 Jonathan Underwood 2019-01-19 23:59:04 UTC 
Another "me too" on F29.
Comment 16 Peter Hutterer 2019-01-25 03:50:17 UTC 
I filed an upstream bug for this: https://gitlab.freedesktop.org/spice/spice-gtk/issues/83
Comment 17 Olivier Fourdan 2019-02-07 09:32:07 UTC 
Scratch build of a test package containing the proposed fixes for this here:

https://koji.fedoraproject.org/koji/taskinfo?taskID=32602301

(Note, being a scratch build, it will be automatically deleted shortly)
Comment 18 Fedora Update System 2019-03-07 11:52:15 UTC 
spice-gtk-0.36-4.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-3ab1ec2646
Comment 19 Fedora Update System 2019-03-07 18:37:24 UTC 
spice-gtk-0.36-4.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-3ab1ec2646
Comment 20 Grzegorz Witkowski 2019-03-07 19:58:15 UTC 
I noticed recently that the issue seem to be already resolved after some updates in F29.
virt-manager-2.1.0-1.fc29.noarch
virt-viewer-7.0-1.fc29.x86_64
pice-gtk3-0.35-3.fc29.x86_64
spice-vdagent-0.18.0-2.fc29.x86_64
Comment 21 Antonio Romito 2019-03-07 22:32:04 UTC 
Grzegorz Witkowski, I've the versions you mentioned, and problem is still there.

[root@localhost ~]# rpm -qa | egrep "virt-manager|virt-viewer|spice-gtk3|spice-vdagent"
virt-manager-2.1.0-1.fc29.noarch
spice-gtk3-0.35-3.fc29.x86_64
virt-viewer-7.0-1.fc29.x86_64
spice-vdagent-0.18.0-2.fc29.x86_64
Comment 23 Fedora Update System 2019-03-29 19:10:48 UTC 
spice-gtk-0.36-4.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.