Problem reported by Simon Mackinlay in the Debian BTS a couple months ago, reproduce here with Xserver 1.3.
There does not seem to be a way to prevent the XINERAMA extension being reported as a supported extension in xdpyinfo; from xorg.conf...
Option "omit XINERAMA"
Option "XINERAMA" "off"
or with -xinerama -disablexineramaextension on the command line.
$ xdpyinfo | grep XINERAMA
.... ordinarily this wouldn't be an issue but some X11 clients use
this (presence of an extension) as a boolean conditional immediately
prior to requesting extension-specific functions.
It could be related to a similar problem in Xephyr (bug #11118) and to some problem on sparc where XineramaIsActive and XineramaQueryScreens disagree (bug #11504).
I've been affected by this same problem too. I believe it is because Xrandr 1.2 now registers itself to handle the Xinerama calls if Xinerama is not compiled in. It cannot be disabled with the "Xinerama" flag in the "ServerFlags" section because checks for that option only exist in X if Xinerama was enabled at compile time.
I've just posted to the xorg list about this change in behaviour: http://lists.freedesktop.org/archives/xorg/2007-November/030610.html
*** Bug 11118 has been marked as a duplicate of this bug. ***
Xinerama has two parts to it:
- the Xinerama extension as part of the server
- the Xinerama protocol extension
all xorg.conf and commandline options only work on the first - they disable the xinerama extension from loading in the server.
if RandR is initialized, it exposes the xinerama _protocol_ over the wire - yet the xinerama extension is still disabled in the server. The randr and xinerama server extensions are mutually exclusive.
xdpyinfo reports what is exposed over the wire. This bug has been open for 2 years and it is unlikely that this will get fixed anytime soon. Closing as WONTFIX.