<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110417#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110417">bug 110417</a>
from <span class="vcard"><a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> <span class="fn">Alex Deucher</span></a>
</span></b>
<pre>(In reply to tempel.julian from <a href="show_bug.cgi?id=110417#c6">comment #6</a>)
<span class="quote">> Ha, curious. I really could never spot any tearing before the 5.2-wip
> branch. Glad that bisecting is not required.
>
> Well, there is one little exception (independent of the compositor):
> When I turn on RedShift without fading (e.g. "redshift -O 4500"), tearing
> occurs once during enabling/disabling. Happens also with TearFree. Not a big
> deal, just want to mention it once.</span >
I believe that is due to limitations in the atomic API with respect to updates.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>