dyer@spdcc.COM (Steve Dyer) (01/05/90)
Took binaries, libraries, includes of VAX4.3BSD X11R4 installation
over to a uVAX-II/qdss mono system which had heretofore been running
some variant of X10r4.
Everything's in place; no remnants of old X10 stuff around, xterm properly
SUID root, plenty of pseudo-TTYs, /usr/bin/X11/Xqdss linked to /usr/bin/X11/X,
no weird .Xdefaults or .xinitrc files. The X11 unix domain socket gets
created OK. At this point in time, no entries in /etc/ttys for ttyv0/qdss
console (i.e., no getty's sitting waiting). In other words, nothing obviously
wrong.
Symptom: "xinit" invoked manually from another terminal brings up the
gray stipple and mouse cursor, but then terminates with no errors other
than "waiting for X server to terminate.." which it then does. I
suspect that "xterm" is failing, but I'm not sure where to look next.
There are no messages betraying why it's failing.
Is there anything obvious I'm missing before I start rolling up my sleeves?
--
Steve Dyer
dyer@ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer
dyer@arktouros.mit.edu, dyer@hstbme.mit.edukeith@EXPO.LCS.MIT.EDU (Keith Packard) (01/05/90)
> Symptom: "xinit" invoked manually from another terminal brings up the > gray stipple and mouse cursor, but then terminates with no errors other > than "waiting for X server to terminate.." which it then does. I > suspect that "xterm" is failing, but I'm not sure where to look next. > There are no messages betraying why it's failing. xinit is a pretty awful program to use when debugging things like this; when you've got a remote terminal to debug with, I'd suggest starting the server by hand and then try to run xterm (also by hand): $ /usr/bin/X11/Xqdss & (wait until the cursor appears) $ setenv DISPLAY :0 $ /usr/bin/X11/xterm At this point, xterm has a chance to display the troubles it's having and give more meaningful error messages. Keith Packard MIT X Consortium