From owner-freebsd-questions@FreeBSD.ORG Fri Jan 2 06:04:20 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5EB016A4CE for ; Fri, 2 Jan 2004 06:04:20 -0800 (PST) Received: from qsmtp4.america.net (qsmtp4.america.net [69.60.160.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11ECD43D6A for ; Fri, 2 Jan 2004 06:04:14 -0800 (PST) (envelope-from trey@fastmail.fm) Received: from [65.82.45.189] (helo=fastmail.fm) by qsmtp4.america.net with esmtp (Exim 4.10) id 1AcPuP-0007Jb-00; Fri, 02 Jan 2004 09:04:13 -0500 Message-ID: <3FF57BAB.1020804@fastmail.fm> Date: Fri, 02 Jan 2004 09:09:47 -0500 From: Trey Sizemore User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jaroslaw Nozderko References: <200401021231.32584.jarek@eko.net.pl> In-Reply-To: <200401021231.32584.jarek@eko.net.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@FreeBSD.ORG Subject: Re: Problems with startx on 5.2-RC2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jan 2004 14:04:20 -0000 Jaroslaw Nozderko wrote: >OS: FreeBSD 5.2-RC2 (MAC - biba,mls) > >Hi, > > I have problem with X on 5.2-RC2. Sometimes the whole >system hangs when I start X by startx or 'setpmac mls/equal startx' >(with MAC policies loaded). In about 30% of attempts it hangs on >XFree startup messages and hard reset is required. >The problem occurs a little bit too often for some unrelated >accident and it doesn't occur at all on 5.1-RELEASE (the same >hardware and configuration). > >Does anyone have similar problem ? > >Regards, >Jarek > > > Yes, see my post from earlier today called "Can't shutdown, logout, or restart cleanly." I have not run 5.1-RELEASE before, so I can't say if it didn't happen there, but it definitely happens with 5.2-CURRENT. I'm at my wit's end trying to find out why!