Bug 67377

Summary: [sna 4500MHD] Glyph corruption, changes with repaint
Product: xorg Reporter: Russell Haley <yumpusamongus>
Component: Driver/intelAssignee: Chris Wilson <chris>
Status: RESOLVED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: yumpusamongus
Version: 7.7 (2012.06)   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Video of problem
none
Xorg.0.log from xorg 1.12
none
Xorg.0.log from xorg 1.14.99.1-167-gff38bbe
none
Video of problem (correct mime type) none

Description Russell Haley 2013-07-26 21:49:51 UTC 
Created attachment 83062 [details]
Video of problem

Characters are drawn incorrectly with some small probability on every repaint. This causes a few characters on screen to be corrupt most of the time, and makes a rather odd flickering effect when resizing windows.  See attached video for example. Symptoms appear not to be present with bitmap or monospace fonts.

A git bisect suggests the problem appeared here:
http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=2a59eadf8165bd70780ac16220456c6196ac3ff1

It would seem the glyph mask hack is still needed.

I was able to reproduce the problem with xf86-video-intel 2.21.12 on Xorg 1.12 (Debian Sid) and on Xorg 1.14.99.1-167-gff38bbe, built using the instructions in the ModularDevelopersGuide.
Comment 1 Russell Haley 2013-07-26 21:50:58 UTC 
Created attachment 83063 [details]
Xorg.0.log from xorg 1.12
Comment 2 Russell Haley 2013-07-26 21:51:42 UTC 
Created attachment 83064 [details]
Xorg.0.log from xorg 1.14.99.1-167-gff38bbe
Comment 3 Russell Haley 2013-07-26 21:55:09 UTC 
Created attachment 83065 [details]
Video of problem (correct mime type)
Comment 4 Russell Haley 2013-07-26 22:05:44 UTC 
Additional information: kernel version is 3.10.2.
Comment 5 Chris Wilson 2013-07-26 22:25:18 UTC 

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

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.