From owner-freebsd-questions@FreeBSD.ORG  Fri Jan  2 09:41:39 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 377EC16A4CF
	for <freebsd-questions@FreeBSD.ORG>;
	Fri,  2 Jan 2004 09:41:39 -0800 (PST)
Received: from mail.prosoft.com.pl (ns.prosoft.com.pl [213.25.91.194])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CBF5343D48
	for <freebsd-questions@FreeBSD.ORG>;
	Fri,  2 Jan 2004 09:41:37 -0800 (PST)
	(envelope-from jarek@eko.net.pl)
Received: from wa35m26.eko.net.pl ([192.168.78.26] helo=skorpion)
	by mail.prosoft.com.pl with asmtp (Exim 4.22)
	id 1AcSqu-0007hL-CD; Fri, 02 Jan 2004 18:12:48 +0100
From: Jaroslaw Nozderko <jarek@eko.net.pl>
To: Trey Sizemore <trey@fastmail.fm>
Date: Fri, 2 Jan 2004 18:09:08 +0100
User-Agent: KMail/1.5.2
References: <200401021231.32584.jarek@eko.net.pl>
	<3FF57BAB.1020804@fastmail.fm>
In-Reply-To: <3FF57BAB.1020804@fastmail.fm>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200401021809.08096.jarek@eko.net.pl>
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 <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 17:41:39 -0000

Hi Trey,

>
> 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!

thanks, I've read it - I have Asus P3B-F motherboard :))
But seriously, I'm not sure it's hardware-related - I don't remember a
single occurence of this problem in 5.1 and 5.0. It seems to have
something to do with 5.2.

Regards,
Jarek