Bug 20625 - [855] Rendering artifacts
Summary: [855] Rendering artifacts
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.4 (2008.09)
Hardware: Other All
: medium normal
Assignee: Carl Worth
QA Contact: Xorg Project Team
Keywords: NEEDINFO
Depends on:
Reported: 2009-03-12 06:55 UTC by Andrew Moise
Modified: 2009-08-17 14:07 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Screenshot showing xterm corruption (145.18 KB, image/png)
2009-03-12 06:55 UTC, Andrew Moise
no flags Details
xorg.conf (4.16 KB, text/plain)
2009-03-12 06:55 UTC, Andrew Moise
no flags Details
Xorg.0.log (49.07 KB, text/plain)
2009-03-12 06:55 UTC, Andrew Moise
no flags Details

Description Andrew Moise 2009-03-12 06:55:05 UTC
Created attachment 23795 [details]
Screenshot showing xterm corruption

I'm running version 2.6.1-1 of the Intel driver from Debian experimental.  I see a couple of different rendering artifacts.  My screen is rotated; I've seen the first artifact even on a non-rotated screen, but I'm not sure that I've seen the second one on a non-rotated screen.

First, Iceweasel sometimes does not repaint everything (for example, it will get exposed but not repaint the toolbar, so that the toolbar is completely grey until something happens to make it repaint again.)  I'd think that that was an Iceweasel bug, except that when it happens I get a message in my X log: "exaCopyDirty: Pending damage region empty!"

The other I've noticed is that dragging an xterm up and right will sometimes mangle the contents of the xterm.  You can see the results of this in the attached screenshot.

Comment 1 Andrew Moise 2009-03-12 06:55:38 UTC
Created attachment 23796 [details]
Comment 2 Andrew Moise 2009-03-12 06:55:59 UTC
Created attachment 23797 [details]
Comment 3 Eric Anholt 2009-07-15 16:44:47 UTC
Does this also occur with a 2.6.30 kernel?

We've recently fixed some rendering problems with old kernels and the current 2D driver, but it's still not a recommended code path.
Comment 4 Carl Worth 2009-07-31 09:58:06 UTC
I'd also be interested to know if this is happening with UXA, (for example, with driver version 2.8.0 where EXA no longer exists).

Comment 5 Carl Worth 2009-08-17 14:07:55 UTC
Hi Andrew,

Without additional information from you, we're going to assume that the
bug is indeed fixed. If you discover that we are wrong, please feel free
to reopen the bug and supply the additional information.



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.