<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [nouveau] garbled rendering with glamor on G71" href="https://bugs.freedesktop.org/show_bug.cgi?id=99400#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [nouveau] garbled rendering with glamor on G71" href="https://bugs.freedesktop.org/show_bug.cgi?id=99400">bug 99400</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to Olivier Fourdan from <a href="show_bug.cgi?id=99400#c21">comment #21</a>) > Same links, updated files: > > <a href="https://people.freedesktop.org/~ofourdan/bug99400/Xwayland.log">https://people.freedesktop.org/~ofourdan/bug99400/Xwayland.log</a> > <a href="https://people.freedesktop.org/~ofourdan/bug99400/Xwayland.trace">https://people.freedesktop.org/~ofourdan/bug99400/Xwayland.trace</a> > > > For example frame 8932 (toward the end) is interesting imho, [...] > > Let's forget about this, now that the new trace can replay on both intel and > nouveau. > > The problem I see is rather that I see no problem in apitrace, the frames > look fine, AFAICT. Hmmm... this is very unfortunate. And furthermore unfortunate is that this trace makes use of NPOT textures, which my NV34 doesn't support (at least not without some pretty nasty workarounds). If replaying the trace yields the desired results, then this is all for naught. You can try running apitrace dump-images --calls='*/draw' Xwayland.trace and see if any of the screenshots generated show the artifacts. If not, then this is a much more insidious problem.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>