<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#c46">Comment # 46</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 Hans de Goede from <a href="show_bug.cgi?id=90871#c44">comment #44</a>) > Hi Ilia, > > (In reply to Ilia Mirkin from <a href="show_bug.cgi?id=90871#c43">comment #43</a>) > > Created <a href="attachment.cgi?id=118995" name="attach_118995" title="updated test program">attachment 118995</a> <a href="attachment.cgi?id=118995&action=edit" title="updated test program">[details]</a> > > updated test program > > > > With this I get the same results whether I set has_texture_rectangle = 1 or > > 0. Attached the full updated source file, or use the patch below. > > Thanks for the updated test program, this seems to fix things on nv3x. There > still is an issue with then test program though (also reproduced on intel > gfx) the program is supposed to change the color of the "box" when you click > a mouse button (pressing a key exits the program), but currently when using > rectangle textures it draws a red box on startup and then on a mouse click > everything goes gray, where as the box should turn blue. As said this > happens on intel gfx too, so I think there still is an issue with the test > program when using rectangle textures. Just my incompetence -- glMatrixMode has to go *before* glPushMatrix, not after. Oops. Moving it up makes the program behave as expected, at least on intel/hsw. > > As for epoxy not seeing the extension, I believe that that is an epoxy > issue, as said the extension is clearly listed in both glxinfo and glxgears > -info output. 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. I wonder if this is a real issue in xfwm code as well.</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>