DHH102@psuvm.psu.edu (11/27/90)
I just installed X on a network of sun 3/50's with 68881's.
I did the ldconfig, and used gcc with the fixincludes working
properly.. However, when I try startx or xinit to start up
xwindows, everything seems to work fine initially, i.e. the
stiple pattern comes up, the mouse tracks, and even a window
forms, and then everything crashes with the following...
Can someone translate this for me? or suggest what might be
happening or an alternate course of action? thanks
dhh102@psuvm.psu.edu dhh102@psuvm.bitnet
{rutgers,gatech,mcvax}!psuvax1!psuvm.psu.edu!dhh102
------------------------------typescript--------------------
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
waiting for X server to shut down XIO: fatal IO error 32 (Broken pipe) on X
server "unix:0.0"
after 258 requests (256 known processed) with 0 events remaining.
The connection was probably broken by a server shutdown or KillClient.
.
[52]% ^D
script done on Mon Nov 26 19:22:30 1990mouse@LARRY.MCRCIM.MCGILL.EDU (11/27/90)
> 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