[Bug 72375] Corruption in some windows after returning from xlock

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Dec 6 07:12:43 PST 2013


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

--- Comment #3 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Created attachment 90365
  --> https://bugs.freedesktop.org/attachment.cgi?id=90365&action=edit
X log with git intel ddx

Hrmph. Well, try as I might, I was unable to repro this with the latest code.
It also didn't want to repro easily with .906 -- turns out if I run xlock from
the second workspace rather than the first it does repro (?? why would anything
care or even be able to detect it? they both just had an identically-configured
aterm on them). But with latest git (46256fa5a0ca) I couldn't get it to have
the little black squares. I'll switch over to it as soon as is convenient, and
see if I get any more artifacts.

I'm attaching a Xorg log with the git DDX code for posterity, but I guess this
bug can be closed. Sorry for the trouble, and thanks for improving the intel
DDX :) [But don't worry, I'll file more issues.]

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20131206/886bd0fc/attachment.html>


More information about the intel-gfx-bugs mailing list