On Fri, Jul 16, 2004 at 08:57:10AM +0300, Micha Feigin wrote: > On Wed, Jul 14, 2004 at 02:16:00AM -0500, Branden Robinson wrote: > > On Wed, Jul 14, 2004 at 02:13:58AM -0500, Branden Robinson wrote: > > > > Running startx -- :1 when another session of X is already running will > > > > not hang BTW. > > > > Something just occurred to me. > > > > If my guess is right, this will break exactly the same way if you do this: > > > > startx -- :1 -nolisten tcp > > > > Please try that. > > This has the exact same behavior as startx -- :1 or running wdm (I am > guessing you wanted me to run the full .xsession here and not just an > xterm as before). It locks up when no cable is plugged in and there is > no X already running (if X is already running on another display it > doesn't lock). > > It shouldn't be something in .xsession thats locking since wdm also > locks and X locks right on startup before .xsession has a time to be run. > > I tried another thing and just ran X alone (/usr/bin/X11/X), not through > startx. It also locks up on the network timeout. It seems that X the > culprit that's trying to resolve the hostname either when it shouldn't or > in a wrong manner (bypassing /etc/hosts). Okay; my theory was wrong. I am running out of ideas. -- G. Branden Robinson | A fundamentalist is someone who Debian GNU/Linux | hates sin more than he loves branden@debian.org | virtue. http://people.debian.org/~branden/ | -- John H. Schaar
Attachment:
signature.asc
Description: Digital signature