<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Second screen corruption with TearFree and glamor" href="https://bugs.freedesktop.org/show_bug.cgi?id=94751#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Second screen corruption with TearFree and glamor" href="https://bugs.freedesktop.org/show_bug.cgi?id=94751">bug 94751</a> from <a class="email" href="mailto:alex_y_xu@yahoo.ca" title="alex_y_xu@yahoo.ca">alex_y_xu@yahoo.ca</a> <pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=94751#c1">comment #1</a>) > Created <a href="attachment.cgi?id=122630" name="attach_122630" title="Update pixmap pitch in radeon_set_pixmap_bo">attachment 122630</a> <a href="attachment.cgi?id=122630&action=edit" title="Update pixmap pitch in radeon_set_pixmap_bo">[details]</a> <a href='page.cgi?id=splinter.html&bug=94751&attachment=122630'>[review]</a> [review] > Update pixmap pitch in radeon_set_pixmap_bo > > Does this patch fix the problem? If not, please attach the Xorg log and the > output of xrandr captured when the problem occurs. Oh, I forgot to attach Xorg log. I checked xrandr and the output appeared to be correct. I also did "xrandr --output DVI-1 --off" which turned the monitor off, then "xrandr --auto DVI-1" which turned it back on with the same issue. Also, in case it is relevant, the corruption looks similar to blocks of the previous content displayed on the screen. Also, as far as I can tell, the cursor works normally when moved over into that monitor (i.e. displayed "on top" of the corruption), including being Plasma themed. Also, unsurprisingly, spectacle (KDE screenshot utility) displayed the contents of the monitor correctly. > (In reply to alex_y_xu from <a href="show_bug.cgi?id=94751#c0">comment #0</a>) > > I can bisect if necessary, but it would be somewhat inconvenient. > > Why is that? FWIW, you don't even need to quit your main X session for it. Hm, I forgot about that. Still, I would have to figure out how the ebuild works or how to install the driver myself. Not a huge amount of work, but I assumed you can probably accurately guess the problem. > > I would prefer a specific commit to checkout or revert to test. > > My guess would be that > <a href="https://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/">https://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/</a> > ?id=b2b079be0e7ef2704c3df9ee25fe46166e450e83 introduced the problem. OK, I can test in ~18 hours.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>