<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [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#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [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:martin.x.andersen@gmail.com" title="Martin Andersen <martin.x.andersen@gmail.com>"> Martin Andersen</a> <pre>I see. Interesting. I notice the non-working setup is trying to set the focus to the root-window, instead of inheriting the parent: 004:>:1021:32: Reply to GetInputFocus: revert-to=PointerRoot(0x01) focus=PointerRoot(0x00000001) 004:>:1021: Event PropertyNotify(28) window=0x02a00026 So in terms of a possible fix, I guess this will need some deeper digging to see why the apparent disconnect between the application calls and the incorrect DRI2 window placements occur? (Especially if more layers in the gfx-stack are involved.)</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>