From owner-freebsd-questions Wed Nov 22 22:30:03 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA19257 for questions-outgoing; Wed, 22 Nov 1995 22:30:03 -0800 Received: from flowbee.interaccess.com (jaykuri@flowbee.interaccess.com [198.80.0.32]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA19202 for ; Wed, 22 Nov 1995 22:29:59 -0800 Received: (from jaykuri@localhost) by flowbee.interaccess.com (8.7.2/8.6.9) id AAA07205; Thu, 23 Nov 1995 00:19:21 -0600 (CST) Date: Thu, 23 Nov 1995 00:19:20 -0600 (CST) From: Jay Kuri To: Lisa Cozzens cc: freebsd-questions@freebsd.org Subject: Re: X problem... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org Precedence: bulk > xf86config multiple times and reverted to a "safe" /etc/XF86Config to no > avail, so it doesn't seem to be a hardware config problem. What happens > is if I type startx, X seems to load OK and I even see the default screen > with the little "x" mouse cursor, but before olvwm kicks in, X exits with > no error message and returns me to the prompt. Sounds to me like an xinit problem. In your .xinitrc file you have to make sure that one of the programs named is not backgrounded. Basically X shuts down as soon as the last program called in .xinitrc quits. If you have no programs here or you have them all in the background, X will quit just as you described. Remember, whatever program you don't put into the background will be the one that will shut down X. If you ran an xclock as your foreground process (no '&') X would not quit until you killed Xclock. Hope this is the answer, Jay K.