<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Incorrect Rendering in Deus Ex: Mankind Divided in-game menu" href="https://bugs.freedesktop.org/show_bug.cgi?id=107224#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Incorrect Rendering in Deus Ex: Mankind Divided in-game menu" href="https://bugs.freedesktop.org/show_bug.cgi?id=107224">bug 107224</a> from <a class="email" href="mailto:t_arceri@yahoo.com.au" title="Timothy Arceri <t_arceri@yahoo.com.au>"> Timothy Arceri</a> <pre>(In reply to Alex Smith from <a href="show_bug.cgi?id=107224#c7">comment #7</a>) > Thanks for confirming. > > It looks like we have a bug where we fail to identify Mesa properly as a > result of compatibility profile support being added, which causes us to go > down a path for a different driver that incorrectly adds that configuration > option. That then persists even after switching back to an older Mesa > version. > > We're looking into what we can do here, but I can confirm it is not a Mesa > bug. Hmm ... I'm seeing the same issue on a i965 skylake machine that should never have exposed compatibility profile support.</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>