I suspect this is a bug in the xrandr extension.
I can work around it by trapping errors around that call if this is, in
fact, a common bug (as opposed to something specific to your setup, or
your version of the server.) But I'd like to hear what the X folks have
to say about it first, though. Is it valid for
XRRSelectInput (dpy, root, RRScreenChangeNotifyMask);
to return BadValue if the server has already claimed to support the
RANDR extension? That doesn't sound reasonable to me, but that seems to
be what's happening.
Just to make sure this is what's going on, please grab the xscreensaver
source and do this:
./configure
cd driver
make test-randr
./test-randr
and see if you get the same error. You should see something like:
test-randr: 19:12:34: XRRQueryExtension(dpy, ...) ==> 117, 0
test-randr: 19:12:34: XRRQueryVersion(dpy, ...) ==> 1, 1
test-randr: 19:12:34: Screen 0
test-randr: 19:12:34: config changed 277 seconds ago
test-randr: 19:12:34: Available Rotations: 0
test-randr: 19:12:34: Current Rotation: 0
test-randr: 19:12:34: Available Reflections: none
test-randr: 19:12:34: Current Reflections: none
test-randr: 19:12:34: size 0: 4096 x 1536 rates: 85
test-randr: 19:12:34: + size 1: 3200 x 1200 rates: 85
test-randr: 19:12:34: size 2: 2560 x 1024 rates: 85
test-randr: 19:12:34: size 3: 2048 x 768 rates: 170
test-randr: 19:12:34: size 4: 1600 x 600 rates: 85
test-randr: awaiting events...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
