<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c45">Comment # 45</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 <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to <a href="show_bug.cgi?id=82619#c44">comment #44</a>) > Interesting. Are you saying I should drop XMoveWindow and use the change > shown in your last post? I think your window creation is correct without the addition of the XMoveWindow, and that the final placement is being messed up by the WM, judging by awesome, doing the WarpPointer before the MapWindow should prevent that class of "place new windows on the same screen of the mouse" issues. Eliminating the extra XSync (and especially that spurious discard-all-events!) is just for extra polish. Not sure about the XSync around the GL context manipulation though - they shouldn't be required, but I expect that they are there due to experiments.</pre> </div> <hr> You are receiving this mail because: <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>