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 747116 - Cursor animations in Wayland backend are broken
Cursor animations in Wayland backend are broken
Status: RESOLVED DUPLICATE of bug 755465
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-03-31 14:21 UTC by Lyude
Modified: 2015-10-13 10:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Lyude 2015-03-31 14:21:14 UTC
I'm not sure if this is reproducible on the Gnome compositor, but I can reproduce it reliably on Weston. It seems that the cursor animation timing on the Wayland backend is mostly broken. If you compare the speed of the animation of the, say, watch cursor, it's almost always faster then the one on the X11 backend. The speed of the cursor seems to be rather erratic too. If you launch ./test/testgtk and run the cursor test, every time you take the cursor in and out of proximity of the application surface, the speed is different.
Comment 1 Matthias Clasen 2015-05-12 00:17:45 UTC
I haven't been able to produce differences in animation speed under weston.
Comment 2 Matthias Clasen 2015-08-27 01:42:41 UTC
I don't see a speed difference, but there is clearly something wrong with animated cursors. Ever so often, I see a cursor image appear at the wrong coordinates, and the cursor is visibly flickering.
Comment 3 Christian Stadelmann 2015-09-03 17:33:16 UTC
I found these steps to reproduce comment #2:

1. open nautilus (under wayland). I tested this on Fedora 23 Alpha
2. click on "Other locations"
3. move the mouse cursor

As long as "Other locations" is loading, the mouse cursor wildly jumps around between the correct position and somewhere below (a bit left).
Comment 4 Carlos Garnacho 2015-10-13 10:04:42 UTC
This was all fixed by commit 603ea3b.

*** This bug has been marked as a duplicate of bug 755465 ***