<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#c4">Comment # 4</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#c3">comment #3</a>) > (In reply to Ilia Mirkin from <a href="show_bug.cgi?id=99400#c2">comment #2</a>) > > Not that it's of much consolation, but the nv30 GL driver sucks. There are a > > number of unhandled situations, and I wouldn't be overly surprised if glamor > > were to hit one or several of them. > > Could be a regression, I don't remember seeing those /before/ and the > downstream bugs about black icons are recent as well. > > And there've been some glamor changes in the xserver as well, so it oculd be > /something/ in glamor has changed and doesn't play well with the driver. This may come as some surprise, but nv30 is not a hotbed of development activity. If you can figure out a change in mesa that broke it, that'd be very helpful. Separately, check dmesg - NVIDIA cards tend to yell loudly when we do something wrong.</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>