From owner-freebsd-questions@FreeBSD.ORG Mon Jan 17 17:01:03 2005 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 A90BD16A4D0 for ; Mon, 17 Jan 2005 17:01:03 +0000 (GMT) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 493A443D1F for ; Mon, 17 Jan 2005 17:01:03 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend2.messagingengine.com (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 4810DC4F592 for ; Mon, 17 Jan 2005 12:01:02 -0500 (EST) X-Sasl-enc: 3NFiZDK0s6zH3IeAJj8eYA 1105981260 Received: from gumby.localhost (dsl-80-41-73-239.access.uk.tiscali.com [80.41.73.239]) by frontend2.messagingengine.com (Postfix) with ESMTP id 7D35456F785 for ; Mon, 17 Jan 2005 12:01:00 -0500 (EST) From: RW To: freebsd-questions@freebsd.org Date: Mon, 17 Jan 2005 17:00:55 +0000 User-Agent: KMail/1.7.2 References: <20050117111737.GB5301@internode.com.au> <41EBEC3B.7030606@makeworld.com> In-Reply-To: <41EBEC3B.7030606@makeworld.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501171700.55945.list-freebsd-2004@morbius.sent.com> Subject: Re: KDE issues after upgrade 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: Mon, 17 Jan 2005 17:01:03 -0000 On Monday 17 January 2005 16:47, Chris wrote: > Adam Smith wrote: > >What happens is, upon loading of KDE from KDM, just after "Initializing > >Peripherals", it backs out with no error and Xorg reloads. > >Anyone got any suggestions as to what I might try to resolve this problem? > > When ever you pull off a cvsup of the ports tree, you MUST, again - MUST > read /usr/ports/UPDATING > to view additional instructions, issues, etc. That should be the 2nd > thing you do. 1st being the actual cvsup. > > Read that file and see if anything pops out at you. See the 20041229 entry in particular.