<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - EGL_KHR_gl_colorspace (v2) causes problem with Android-x86 GUI" href="https://bugs.freedesktop.org/show_bug.cgi?id=91596#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - EGL_KHR_gl_colorspace (v2) causes problem with Android-x86 GUI" href="https://bugs.freedesktop.org/show_bug.cgi?id=91596">bug 91596</a> from <a class="email" href="mailto:emil.l.velikov@gmail.com" title="Emil Velikov <emil.l.velikov@gmail.com>"> Emil Velikov</a> <pre>(In reply to Emil Velikov from <a href="show_bug.cgi?id=91596#c14">comment #14</a>) > (In reply to Ilia Mirkin from <a href="show_bug.cgi?id=91596#c13">comment #13</a>) > > Er nevermind. Before it was malloc'd but now it's calloc'd. > > The most creepy part is that with the extension disabled, we can never get > to the srgb configs, as GLColorspace will be LINEAR. Even if the user > requests one, we'll error out. Actually I stand corrected - if one disables the extension, we'll still expose/list the srgb configs. With this patch [1] + the one in <a href="show_bug.cgi?id=91596#c8">comment 8</a> things should be back to normal. Now we need to figure out why things go crazy in the first place (hint check the format mappings in <a href="show_bug.cgi?id=91596#c15">comment 15</a>). [1] <a href="http://patchwork.freedesktop.org/patch/60961/">http://patchwork.freedesktop.org/patch/60961/</a></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>