<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - NV30: Xfwm4 use_compositing - garbled display" href="https://bugs.freedesktop.org/show_bug.cgi?id=90871#c48">Comment # 48</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - NV30: Xfwm4 use_compositing - garbled display" href="https://bugs.freedesktop.org/show_bug.cgi?id=90871">bug 90871</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=90871#c47">comment #47</a>) > (In reply to Ilia Mirkin from <a href="show_bug.cgi?id=90871#c46">comment #46</a>) > > Pretty sure it's what I said -- the test program doesn't do a glXMakeCurrent > > before calling gl functions, which means their output is invalid. Not an > > epoxy issue. Rearranging the test program's code to fix this is annoying > > though. > > No it's not, if the test program is invalid, it ought to be fixed. > > > I wonder if this is a real issue in xfwm code as well. > > Yes, most likely. This code is still early beta in xfwm4. I'll try to fix it > and Poma will be able to test I guess. The main reason why it's annoying to fix in the test program is that you use that knowledge for selecting fbconfigs... which you need to do before making a context current. Now you could either (a) do a 2-step process whereby you first see if the ext is there, and then go and select another config or (b) make the assumption that rect support is an all-or-nothing thing -- either no configs have it or they all do, so no need to check it when evaluating fbconfig validity. I'm moderately sure that'd be a valid assumption.</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>