[Bug 104461] [regression][bisected] Moving mouse in some games under wine causes mouse flicker and low performance

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jan 31 19:11:52 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=104461

Ville Syrjala <ville.syrjala at linux.intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |NOTOURBUG

--- Comment #5 from Ville Syrjala <ville.syrjala at linux.intel.com> ---
Looks like a bug/feature of the game (or maybe wine) that it actually keeps
turning the cursor off and on all the time. That causes us to drop off the
unthrottled cursor fastpath. No idea why the game/wine does that. Can't imagine
anyone wants to look at a randomly flickering cursor for length of time.

The following hack in wine will eliminate the problem, but it would also leave
a stale cursor on screen if the game actually wants to turn the cursor off:

diff --git a/dlls/winex11.drv/mouse.c b/dlls/winex11.drv/mouse.c
index 186899fb16..9aaa9a18f9 100644
--- a/dlls/winex11.drv/mouse.c
+++ b/dlls/winex11.drv/mouse.c
@@ -223,6 +223,8 @@ void set_window_cursor( Window window, HCURSOR handle )
         XUnlockDisplay( gdi_display );
     }

+    if (!handle)
+      return;
     XDefineCursor( gdi_display, window, cursor );
     /* make the change take effect immediately */
     XFlush( gdi_display );

While making all cursor updates unthrottled would be possible from the hardware
point of view, it'd be a lot of work to shoehorn that into the current driver
architecture. So I'm going declare this as "not our bug" and move on ;)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180131/83e5bd74/attachment.html>


More information about the intel-gfx-bugs mailing list