<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Mesa 17.2 no longer can give SRGB-capable framebuffer on i965, even though Mesa 17.1.x does." href="https://bugs.freedesktop.org/show_bug.cgi?id=102354#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Mesa 17.2 no longer can give SRGB-capable framebuffer on i965, even though Mesa 17.1.x does." href="https://bugs.freedesktop.org/show_bug.cgi?id=102354">bug 102354</a> from <a class="email" href="mailto:deveee@gmail.com" title="Deve <deveee@gmail.com>"> Deve</a> <pre>I just checked the patch and nothing changed for me (with GLX, I didn't test EGL). I patched mesa version 4d807d7fe272db97fb9e20800872d5970fa2696d. If you run current git STK, there are two warnings in console: [warn ] irr_driver: Created visual is not sRGB-capable. Re-creating device to workaround the issue. [warn ] [IrrDriver Temp Logger]: Level 2: No sRGB framebuffer available. The first one happens for intel when glGetFramebufferAttachmentParameteriv(GL_DRAW_FRAMEBUFFER, GL_BACK_LEFT, GL_FRAMEBUFFER_ATTACHMENT_COLOR_ENCODING, &param); returns GL_LINEAR, so this is true for all mesa versions >= 10.6 (precisely since MESA_FORMAT_R8G8B8X8_UNORM has been added). In this case we make an ugly hack and re-create device with alpha channel, that forces to use MESA_FORMAT_R8G8B8A8_SRGB. The second warning happens when request a config with GLX_FRAMEBUFFER_SRGB_CAPABLE_ARB fails. So then we try to get a config without this flag. And glxinfo still doesn't show any srgb configs for me. Are there some particular requirements, such as current libdrm, DRI2/DRI3 etc...?</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>