<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - [regression] recent ABI changes in xorg-video-intel (intel_drv.so) breaks dual-head XBMC"
href="https://bugs.freedesktop.org/show_bug.cgi?id=82619#c50">Comment # 50</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - [regression] recent ABI changes in xorg-video-intel (intel_drv.so) breaks dual-head XBMC"
href="https://bugs.freedesktop.org/show_bug.cgi?id=82619">bug 82619</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>In my awesome, example no. I ran the entire session under xtrace and watched
the configure requests go into the WM and be transformed there. In that case,
it is quite easy to see how there would be a race between moving the mouse and
the position of a new window. (I am pretty sure mutter and unity do the same
placement on screen next to mouse as well.) However, I'll need to dig into
fluxbox to see what is going on there.</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 on the CC list for the bug.</li>
</ul>
</body>
</html>