<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [nouveau] garbled rendering with glamor on G71"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99400#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [nouveau] garbled rendering with glamor on G71"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99400">bug 99400</a>
from <span class="vcard"><a class="email" href="mailto:fourdan@xfce.org" title="Olivier Fourdan <fourdan@xfce.org>"> <span class="fn">Olivier Fourdan</span></a>
</span></b>
<pre>(In reply to Ilia Mirkin from <a href="show_bug.cgi?id=99400#c13">comment #13</a>)
<span class="quote">> I'd like to help you, but I'm just not sure how -- I don't have Wayland (or
> any interest in setting that up), and your traces appear incomplete. I don't
> know why - I've never seen that before. But they don't create contexts.
> [...]
> While the Xwayland trace has none of those. Paradoxically, it starts at call
> 31. Perhaps you have a non-egl-enabled apitrace? Also note that there's not
> a single instance of UseProgram or any other shader-related items in the
> XWayland trace.</span >
Oh right... Blimey! You got me thinking here, you're right, those Xwayland
traces are just wrong, it's libepoxy not playing nice with "apitrace --api-egl"
(<a href="https://github.com/anholt/libepoxy/issues/68">https://github.com/anholt/libepoxy/issues/68</a>) so I picked up the forked
version libexpoy, rebuilt apitrace and Xwayland and was able to capture a much
better trace!</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>