Bug 107960 - XFixesGetCursorImage returns empty cursor with first frame
Summary: XFixesGetCursorImage returns empty cursor with first frame
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-17 11:53 UTC by Peter Åstrand
Modified: 2018-12-13 22:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Gold theme - tar.bz2 of ~/.icons (721.18 KB, application/octet-stream)
2018-09-17 11:57 UTC, Peter Åstrand
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Åstrand 2018-09-17 11:53:07 UTC
This bug is similar to https://bugzilla.redhat.com/show_bug.cgi?id=1542289 / https://cgit.freedesktop.org/xorg/xserver/commit/xfixes/cursor.c?id=ceaf4277447407a7430b9bc3205462fbdbae0e39, but this is still a problem with 1.20. I have an animated cursor theme where the cursor animates only every ~8 seconds or so. In this case, XFixesGetCursorImage will return a 1x1 invisible cursor until 8 seconds has passed. This worked correctly with Xorg server 1.14.
Comment 1 Peter Åstrand 2018-09-17 11:57:03 UTC
Created attachment 141602 [details]
Gold theme - tar.bz2 of ~/.icons

The attached theme triggers the bug, for example when moving from the URL field in Firefox to a blank area in a new tab. Verified in XFCE on CentOS 6.
Comment 2 GitLab Migration User 2018-12-13 22:40:53 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/548.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.