Note that Xinerama does not appear to be in the process of being deprecated. The wikipedia article was modified a year ago, describing the old words as "full of lies": <http://en.wikipedia.org/w/index.php?title=Xinerama&diff=421530795&oldid=415820495>. Nothing on x.org seems to lead to deprecation. Instead, issues like conflicting with compositing have been fixed.
I think the fundamental flaw here is in how XRANDR and Xinerama interact in the X server. Enabling Xinerama shouldn't disable the XRANDR extension protocol. It should instead allow all of the read-only operations (allowing `xrandr -q` to work); and return errors for attempts to actually *change* things which would conflict with Xinerama. All of which is, obviously, upstream work. Both Xinerama and XRANDR would need some work, plus -nvidia to stop forcibly disabling XRANDR when Xinerama is active. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/157319 Title: Xlib: extension "RANDR" missing on display ":0.0" while using -nvidia with Xinerama turned on To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/157319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
