Newsgroups: comp.windows.x
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!mit-eddie!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU
Subject: Re:  problems with xlock
Message-ID: <9008092311.AA16945@Larry.McRCIM.McGill.EDU>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Date: 9 Aug 90 23:11:22 GMT
Lines: 22

> Some of our users are having problems when they run xlock.  It will
> blank the screen, and then immediately exit with the message:

>  X Error of failed request:  BadValue (integer parameter out of range for operation)
>    Major opcode of failed request:  26 (X_GrabPointer)
>    Minor opcode of failed request:  0
>    Resource id in failed request:  0xffff

Almost certainly, xlock is doing a GrabPointer with an event-mask of
~0, or -1, or some such.  This is wrong; the event-mask is not allowed
to specify bits that do not correspond to anything valid.  The R3
server carelessly let clients get away with this; the R4 server checks
things properly.

The correct fix is to make xlock pass a proper event mask.  If you
can't/won't do this, for whatever reason, you can also put the R4
server into bug-compatibility mode with "xset bc".

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu