[Bug 82619] [regression] recent ABI changes in xorg-video-intel (intel_drv.so) breaks dual-head XBMC
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Aug 21 03:05:10 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=82619
--- Comment #26 from Martin Andersen <martin.x.andersen at gmail.com> ---
> To clarify, it switched between desktops with Cinnamon and failed with everything else?
Sorry for the late reply; I had to pull the xrandr output from a system at a
different location (and obviously xrandr requires you to have a local X
session)
I have not tested the 'XMoveWindow-patch' with WMs other than Cinnamon. I did
however test XBMC with numerous other WMs before (both with the older i965
driver and current ones), and found Cinnamon to be the one which behaved most
correctly/seamlessly.
For instance, fluxbox (which the XBMC devs insist on using), as well as IceWM,
and XFCE4, never acknowledged the xrandr settings at all, despite manually
setting these before and during an XBMC run. It always outputted on the first
available port, at 0,0 coordinates. (This was on the working setup, i.e the
1.2.1 driver.)
With 1.2.1 Unity however appeared to work; although it outputed everything in
60Hz (same as the GUI), and not 23.97Hz (from my custom Xorg.conf modeline),
which it is supposed to.
The only thing not working properly-either as a result of the drivers or the
dual-head config-is proper 50Hz output. It is juddery.
And also the "pure" 23.976Hz (or 23.976023976 to be finicky) output that I
mentioned before on Ivy Bridge which I am unsure actually _can_ be fixed at the
driver level. (Still drops a frame once every few minutes)
> $ xrandr --verbose
> on working / broken setups?
I've included this output as attachments.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140821/7451cccf/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list