[Bug 94677] xorg-server 1.18.2: missing mouse pointer when coming back from screen lock

[bugzilla-daemon at freedesktop.org]

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

--- Comment #4 from Denis Dupeyron <calchan at gentoo.org> ---
Created attachment 122577
  --> https://bugs.freedesktop.org/attachment.cgi?id=122577&action=edit
/sys/kernel/debug/dri/0/i915_display_info

This is a cat of /sys/kernel/debug/dri/0/i915_display_info when the cursor is
invisible. The before and after screenlock diff is this:

--- before    2016-03-26 11:12:18.744047285 -0600
+++ after    2016-03-26 11:13:28.722867306 -0600
@@ -6,11 +6,11 @@
     fb: 50, pos: 0x0, size: 1280x800
     encoder 26: type: LVDS-26, connectors:
         connector 25: type: LVDS-1, status: connected, mode:
-        id 0:"1280x800" freq 60 clock 82060 hdisp 1280 hss 1332 hse 1396 htot
1672 vdisp 800 vss 803 vse 806 vtot 818 type 0x48 flags 0xa
-    cursor visible? yes, position (365, 188), size 64x64, addr 0x00816000,
active? yes
+        id 0:"1280x800" freq 60 clock 82060 hdisp 1280 hss 1332 hse 1396 htot
1672 vdisp 800 vss 803 vse 806 vtot 818 type 0x0 flags 0xa
+    cursor visible? no, position (0, 0), size 0x0, addr 0x00000000, active? no
     No scalers available on this platform
     --Plane id 22: type=PRI, crtc_pos=   0x   0, crtc_size=1280x 800,
src_pos=0.0000x0.0000, src_size=1280.0000x800.0000, format=XR24 little-endian
(0x34325258), rotation=0 (0x00000001)
-    --Plane id 23: type=CUR, crtc_pos= 365x 188, crtc_size=  64x  64,
src_pos=0.0000x0.0000, src_size=64.0000x64.0000, format=AR24 little-endian
(0x34325241), rotation=0 (0x00000001)
+    --Plane id 23: type=CUR, crtc_pos=   0x   0, crtc_size=   0x   0,
src_pos=0.0000x0.0000, src_size=0.0000x0.0000, format=N/A, rotation=0
(0x00000001)
     underrun reporting: cpu=yes pch=no 

 Connector info

-- 
You are receiving this mail because:
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/20160326/05a10613/attachment.html>