<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Qt Programs occasionally fail to render with new Mesa (glGetProgramBinary)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105065#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Qt Programs occasionally fail to render with new Mesa (glGetProgramBinary)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105065">bug 105065</a>
from <span class="vcard"><a class="email" href="mailto:scott.d.phillips@intel.com" title="Scott D Phillips <scott.d.phillips@intel.com>"> <span class="fn">Scott D Phillips</span></a>
</span></b>
<pre>(In reply to Jordan Justen from <a href="show_bug.cgi?id=105065#c4">comment #4</a>)
<span class="quote">> Scott also found that the one app he tested was using compatibility
> profile. If basically all QT apps also use compatibility profile,
> then not exposing it for compatibility profiles might be another
> way to work around the QT bug.</span >
Specifically, this issue in QT will only happen with compat contexts. With a
non-compat context, Step 4 in my list above will result in LINK_STATUS=FALSE
and QT will go down the recompiling path.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>