Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!mips!apple!snorkelwacker!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU
Newsgroups: comp.windows.x
Subject: Re: Crash in XGrabpoiter X11R4
Message-ID: <9010060439.AA05409@Larry.McRCIM.McGill.EDU>
Date: 6 Oct 90 04:39:12 GMT
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 27

>>> I am runnign X11R4 under SunOs 4.1.  When I make a call to
>>> XGrabPoiter I get the following X error message:

>>> X windows Protocol error: BadValue (integer parameter out of range for operation)
>>>      Major opcode of failed request:  26
>>>      Minor opcode of failed request: 0
>>>      Resource id in failed request: 0x8038
>>>      Serial number of failed request: 553

> The other day I posted a message regarding a problem with xterm and
> xman after building X11 under SunOS4.1.  This is exactly the X error
> message I was getting.  So what's going on??

Exactly?  I have no idea then.  Or was the major opcode still 26, but
the "Resource id" something else?  Or was the major opcode different?

I suspect you are somehow running an R3 xterm which has the bug about
passing ~0 as the event-mask to things like XGrabPointer.  If "xset bc"
hides the problem this is probably what's happening.  The proper fix,
of course, is to use a version of xterm that isn't buggy.  If that's
not possible for some reason, using "xset bc" is an acceptable
workaround until you can get a working xterm.

					der Mouse

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