Subject: -current and X386 2.1
To: None <>
From: Brian Moore <>
List: current-users
Date: 04/26/1994 03:54:54
Does anybody use xdm with the latest ( April 23 ) sources?  The problem I am
having is that xdm will let a user log in one time after it starts, but then
when the user logs out, the screen goes back to the pc3 console and hangs. (
This is using xdm with -nodaemon from the command line )  I have the debug
output from xdm and it seems that it is a problem where it tries to reopen the
display.  Here's the tail end of the debug output:

Before XOpenDisplay(:0)
display manager caught SIGUSR1
select returns -1.  Rescan: 0  ChildReady: 0
hung in open, aborting
giving up on server
select returns -1.  Rescan: 0  ChildReady: 1
signals blocked, mask was 0x0
Manager wait returns pid: 442 sig 0 core 0 code 4
Display exited with OPENFAILED_DISPLAY, try 0 of 4

Here's the tail end of the xdm-errors file

Caught signal 11.  Server aborting
error (pid 442): Hung in XOpenDisplay(:0), aborting
error (pid 442): server open failed for :0, giving up
error (pid 393): Display :0 cannot be opened

The crazy thing about this is that everything in X and -current works great,
except for this.  I'd like to be able to get this fixed so I can help track the
X11 sources with the latest -current ( gid_t, uid_t, off_t changes, etc...).
Needless to say, I'm going to be much help until I can figure this one out.
Speaking of this, is there a group of people who are trying to track X386 with
-current?  If so, I'd like to help out on this.

Brian Moore