<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - upgrade from 10.0.3 to 10.1.0 causes all composited windows (texture from pixmap) to become black" href="https://bugs.freedesktop.org/show_bug.cgi?id=76388#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - upgrade from 10.0.3 to 10.1.0 causes all composited windows (texture from pixmap) to become black" href="https://bugs.freedesktop.org/show_bug.cgi?id=76388">bug 76388</a> from <a class="email" href="mailto:raster@rasterman.com" title="Carsten Haitzler <raster@rasterman.com>"> Carsten Haitzler</a> <pre>it's not e that handles y invert - it's evas (library e relies on) and it does handle it - correctly. it was actually our added support of yinvert extension for egl/gles that caught the bug in #73371. since we started handling it on egl/gles on intel drivers pixmaps are inverted. in this case pixmaps are just plain all black - no pixel data at all. everything blank. a downgrade to 10.0.3 fixes that. in fact it seems to vary from machine to machine. on some intel gfx systems it is 100% of the time black. on others its intermittent - depends on boot. reboot and then it works just fine, until randomly a boot later it's black again. i think sandybridge is always black, ivybridge is "sometimes black". nb - this problem we currently see happening with glx+opengl (not egl/gles). i haven't tried egl/gles as i don't normally need/want it).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>