<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#c42">Comment # 42</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>Not sure what is going on here. Which window manager are you testing with? XBMC has behaved consistently with all three systems I've tested on–the first was a Ubuntu Raring (13.04) IVB system upgraded to Saucy (13.10) with the provided i965, libdrm, libva packages. That system was later manually upgraded (packaged the debs myself) and tested with: - xserver-xorg-video-intel_2.99.911 - libva-intel-driver_1.3.1 - libva_1.3.1 - libva-x11-1_1.3.1 - vainfo_1.3.1-1 - libva-drm1_1.3.1 - libva-glx1_1.3.1 - libdrm2_2.4.54 - libdrm-intel1_2.4.54 And the problem re-appeared. Downgrading those to the known-good versions mentioned earlier resolved the issue (using the exact same XBMC version) I also tested it on a fresh Mint 16 installation (also on IVB) (using packages from Saucy/13.10 from which it is based), and reproduced it. The latest test system is an ArchLinux derivative (Manjaro) (on HWE), which runs the following: - xf86-video-intel 2.99.912-2 - libva 1.3.1-2 - libva-intel-driver 1.3.2-1 - libdrm 2.4.56-1 The Mint 16 / Ubuntu 13.10 test systems used the provided packages for 13.10 from 01.org, which at the time were: - libva 1.2.1 - libdrm 2.4.46 - xserver-xorg-video-intel 2.99.904 All my latest tests were done with the Cinnamon WM (2.2.13). Mint 16 uses the older 2.0.14. However, I did test a range of WMs earlier, and could not get a single one of them to successfully change the output. One of the specific versions I used (apart from the ones compiled from git) were: <a href="https://launchpad.net/~wsnipex/+archive/ubuntu/xbmc-fernetmenta-master/+build/6167089/+files/xbmc_14.0%7Egit20140709.0500-607950d-0saucy_all.deb">https://launchpad.net/~wsnipex/+archive/ubuntu/xbmc-fernetmenta-master/+build/6167089/+files/xbmc_14.0%7Egit20140709.0500-607950d-0saucy_all.deb</a> <a href="https://launchpad.net/~wsnipex/+archive/ubuntu/xbmc-fernetmenta-master/+build/6167088/+files/xbmc-bin_14.0%7Egit20140709.0500-607950d-0saucy_amd64.deb">https://launchpad.net/~wsnipex/+archive/ubuntu/xbmc-fernetmenta-master/+build/6167088/+files/xbmc-bin_14.0%7Egit20140709.0500-607950d-0saucy_amd64.deb</a> Unsure if that is of any help though. The behaviour you are seeing is not something I've encountered. Are you testing on a laptop? Maybe there is an issue with LVDS that I have not witnessed before.</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>