After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 758210 - Contextual mouse cursors are not shown on X11 apps when running Wayland
Contextual mouse cursors are not shown on X11 apps when running Wayland
Status: RESOLVED NOTGNOME
Product: mutter
Classification: Core
Component: wayland
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks: WaylandRelated
 
 
Reported: 2015-11-17 04:21 UTC by Jean-François Fortin Tam
Modified: 2016-07-18 10:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jean-François Fortin Tam 2015-11-17 04:21:23 UTC
Running apps in X11 mode (such as Pitivi's daily bundles, or the old LibreOffice), you can see that when you put your mouse...

* over the edge of a window,
* over a Gtk Paned,
* on something that would normally make the cursor change appearance,

...the cursor will remain a normal arrow.
Comment 1 Daniel Stone 2015-11-18 15:43:26 UTC
Works for me with Chrome, but this is pretty dependent on the version of XWayland you're running. Previous ones (basically anything but Git master) were unbearably buggy. Which version are you running? jhbuild will handle master for you.
Comment 2 Jonas Ådahl 2015-11-25 12:31:22 UTC
Could this potentially be something that the invalidate-cursor-sprite-on-enter patch fixes?
Comment 3 Daniel Stone 2015-11-25 13:46:06 UTC
Yeah, that was my guess. I wasn't just CCing you because I like throwing random bugs at you! :)
Comment 4 Matthias Clasen 2015-11-30 16:19:12 UTC
And I assume that is an xwayland patch ? Can we get a link here, to track its progress towards mainline X ?
Comment 6 Olivier Fourdan 2015-12-02 08:06:52 UTC
Jonas' patch has now been pushed upstream as commit 07941a5:

http://cgit.freedesktop.org/xorg/xserver/commit/?id=07941a5
Comment 7 Christian Stadelmann 2016-07-17 10:16:32 UTC
This bug has been fixed and is not present any more on Fedora 24.