A typical case for this is a driver that doesn't support rendering to PICT_A8 destinations. The problem was introduced with the GlyphCache. I tried to locate the problem, but could find no obvious cause. The problem seems to hardware independent. I just wanted to report it officially, so it doesn't get lost.
The bad beheaviour disappears if i disable the migration optimisation, so there's probably a problem with the damage reporting somewhere. Haven't narrowed it down further yet.
If EXA optimizations are broken, they should be disabled. Blocking core optimizations due to broken optimizations for broken drivers is not the way forward.
(In reply to comment #2) > If EXA optimizations are broken, they should be disabled. Blocking core > optimizations What's blocking what? > due to broken optimizations for broken drivers is not the way forward. The optimization only does the wrong thing when damage isn't tracked correctly. Apparently that's the case somewhere in the glyph cache code.
commit 21c116219cd5c6845a0955f2d88fdb5fab5c17cf Author: Michel Dänzer <michel@tungstengraphics.com> Date: Sat Nov 8 01:25:14 2008 +0100 Fix typos which caused exaCompositeRects() to use an incorrect damage region. Thanks to Maarten for spotting the second typo.
*** Bug 18019 has been marked as a duplicate of this bug. ***
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.