From owner-freebsd-current Mon Apr 14 06:16:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA10821 for current-outgoing; Mon, 14 Apr 1997 06:16:25 -0700 (PDT) Received: from tatooine.vader.org (tatooine.vader.org [194.159.100.200]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA10811 for ; Mon, 14 Apr 1997 06:16:22 -0700 (PDT) Received: (from chris@localhost) by tatooine.vader.org (8.8.5/8.8.5) id OAA03676; Mon, 14 Apr 1997 14:16:08 +0100 (BST) From: Chris Dabrowski Message-Id: <199704141316.OAA03676@tatooine.vader.org> Subject: Re: X still broken? In-Reply-To: <199704132337.TAA00472@khavrinen.lcs.mit.edu> from Garrett Wollman at "Apr 13, 97 07:37:49 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Mon, 14 Apr 1997 14:16:08 +0100 (BST) Cc: current@freebsd.org Reply-To: chris@vader.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a previous message, Garrett Wollman wrote: > Today was the day that I would finally get to test out a lot of > changes to the networking code that I had planned. However, when I > rebooted my machine, I found that X is still utterly broken. I don't > think that my changes are to blame, since they are not actually > functional, and in any case the rest of the machine appears to work > Just Fine(tm). The symptom is very simple: any attempt to start the X > server, whether through xdm or startx, puts the system in an infinite > loop where the server starts, and then immediately shuts down and > restarts, all the while locking up the keyboard so that one can't log > in to kill it. > Try changing the permissions of /usr/X11R6/lib/X11/xinit/xinitrc and ~/.xinitrc to 555. Some other people on this list (including myself) were having the same problem and this solution fixed it. Don't ask me why it works though. :-) Chris -- Chris Dabrowski chris@vader.org