Comment 42 for bug 197153

Excellent news that the gnome-desktop changed fixed the problems on radeonhd. I'll forward the fix upstream.

I'd like to hear from the folks on intel with this problem, to see if it solves the issue there as well.

Rick, Xinerama and Xrandr are sort of ying and yang; Xinerama being the old, deprecated method and Xrandr the future. These days only a few drivers (such as the proprietary ones) still support Xinerama. Screens and Graphics (aka displayconfig-gtk) is a Xinerama-based tool; it was developed back before Xrandr was very widely available. These days with so many drivers now using Xrandr, this has rendered displayconfig-gtk obsolete. Thus these efforts into switching over to this new Xrandr config tool.

So the plan is to drop displayconfig-gtk. For all the Xrandr based drivers, this new tool will be better (the only remaining missing capability is driver switching, but I guess we can go back to xorg.conf editing for that for now). For proprietary drivers, nvidia and fglrx both include their own config update tools. The remaining non-Xrandr drivers are much less commonly used; often they're deployed using static xorg.conf's anyway.

Thanks for the swift testing guys. Seb128, based on rbmorse's tests, the g-s-d change should be uploaded as well. It just adds checks that xrandr 1.2 is present (as jcristau suggested yesterday), so should be very safe and regression free.