Description of problem: On different applications running in XWayland, including firefox and eclipse (started using GDK_BACKEND=x11) and some gtk2+python2 applications, the mouse cursor doesn't change any more when e.g. hovering on links. Sometimes it completely disappears. Sometimes you see a text cursor for all of the GUI, including buttons, links, …. Sometimes you see resize cursors until you click somewhere into your application's window. Version-Release number of selected component (if applicable): libwayland-client-1.9.0-1.fc23.x86_64 libwayland-cursor-1.9.0-1.fc23.x86_64 libwayland-server-1.9.0-1.fc23.x86_64 xorg-x11-server-Xwayland-1.18.0-0.6.20151027.fc23.x86_64 How reproducible: The "mouse pointer doesn't change" part: reliably The "mouse pointer disappears" part: not quite reliably Additional info: This issue doesn't affect pure Gtk3 applications running with wayland backend as e.g. gedit, nautilus, evolution. I could not reproduce this issue on a gnome+X session, only on Gnome+Wayland.
The followign patch Jonas sent to the xorg-devel mailing list for Xwayland might help here: http://lists.freedesktop.org/archives/xorg-devel/2015-October/047541.html
*** Bug 1282818 has been marked as a duplicate of this bug. ***
*** Bug 1286342 has been marked as a duplicate of this bug. ***
Jonas' patch menetioned in comment 1 has now been pushed upstream as commit 07941a5: http://cgit.freedesktop.org/xorg/xserver/commit/?id=07941a5
Maybe you can review the attached video on this comment: https://bugzilla.redhat.com/show_bug.cgi?id=1268495#c10 The cursor seems to be stuck when changing shapes on Wayland GTK3 apps.
This issue will be fixed in the next xorg xserver release. (In reply to Anass Ahmed from comment #5) > Maybe you can review the attached video on this comment: > https://bugzilla.redhat.com/show_bug.cgi?id=1268495#c10 > > The cursor seems to be stuck when changing shapes on Wayland GTK3 apps. I think you mean it doesn't get changed when moving onto another window. I can see that and it looks like you are running into the same issue. *** This bug has been marked as a duplicate of bug 1135661 ***