Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!think.com!snorkelwacker.mit.edu!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU
Newsgroups: comp.windows.x
Subject: Re:  Advice on opcode errors running x.
Message-ID: <9011270612.AA02756@Larry.McRCIM.McGill.EDU>
Date: 27 Nov 90 06:12:28 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 44

> When I try startx or xinit to start up xwindows, everything seems to
> work fine initially, i.e. the stip[p]le pattern comes up, the mouse
> tracks, and even a window forms, and then everything crashes with the
> following...

> Script started on Mon Nov 26 19:19:19 1990
> xinit
> [51]% 
> xterm:  warning, error event receieved:
> X Error of failed request:  BadValue (integer parameter out of range for
> operation)
>   Major opcode of failed request:  28 (X_GrabButton)
>   Minor opcode of failed request:  0
>   Resource id in failed request:  0xc
>   Serial number of failed request:  45
>   Current serial number in output stream:  51

I can't really help you solve it.  About all I can do is translate it.
(I assume you've tried rebuilding xterm.  If you're using shared
libraries, you might try linking it statically; I've seen some odd
things go away when this is done.  It usually indicates a problem with
the libraries, but trying it should narrow down the possibilities.)

This is telling you that the client made a GrabButton protocol request,
which corresponds to only one Xlib call: XGrabButton.  The error is
BadValue, which normally means that some argument value is out of
bounds; checking the MIT sample server source indicates that this is
the case for GrabButton.  We are not told *which* argument is out of
bounds, annoyingly.  Looking at the arguments to the GrabButton
request, I find an interesting thing: 0xc is valid value for only two
of them (modifiers and event_mask), unless possibly 0xc is a valid
Window or Cursor ID.  (0xc specifies Control|Mod1 for modifiers, or
ButtonPress|ButtonRelease for event_mask.)

If you really want to find out which argument is responsible, I would
suggest logging in over the network or on a terminal line, starting
Xsun "by hand" (eg, "Xsun -debug &"), starting xscope to watch the
protocol requests, and then starting xterm by hand as well.  xscope
should then reveal precisely what is wrong with the GrabButton request.

					der Mouse

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