Comment 8 for bug 134464

See also bug #150769 which is probably the same.

I see similar corruption consistently when using an external monitor 1680x1050. There is no need for suspend/resume. Merely dragging a window round will produce it. With my laptop screen I never see it, at 1280x1024.

It is easily reproduced in my setup: it's there from the start, or it's not (with the right older driver).

The artifact looks suspiciously like problems in a 2d acceleration op such as block copy/fill. It is not a problem displaying the framebuffer contents, because it can be drawn over with the correct pixels, so it's definitely a drawing problem of some kind. It's not 3d related: I'm not using any 3d acceleration - no Compiz, etc.

This bug was fixed in an older version of the Intel X.Org driver, and got fixed around 2.0.0. The Feisty version of the Intel driver on burtonini.com worked well. But the bug seems to have reappeared in Gutsy's version for quite some time. Unfortunately I forget when exactly it reappeared, as I assumed it would be so obvious that it would get fixed quickly, but it hasn't been fixed for several Intel driver updates in Gutsy.

Because it was fixed for a while, I suspect this is a known fixed bug in X.Org's version which got lost during some code merging accident.