<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#c17">Comment # 17</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: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#c16">comment #16</a>) > 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) Don't worry, this is just noise from XSync() (which generates a round-trip and querying the focus on the root window is a request which should be impossible to generate an error, and so safest to use). > 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.) Yeah, it seems simple enough that it can no longer find something it was looking for, but I can't see what. I'll try and get xbmc setup this week on a multimonitor and see if I can trace the problem.</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>