From owner-freebsd-questions@FreeBSD.ORG Tue May 4 19:59:46 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CFCBB106564A for ; Tue, 4 May 2010 19:59:46 +0000 (UTC) (envelope-from jg@fantomatic.co.uk) Received: from fix.fantomatic.co.uk (fix.fantomatic.co.uk [81.174.154.245]) by mx1.freebsd.org (Postfix) with ESMTP id 2ED6D8FC1E for ; Tue, 4 May 2010 19:59:45 +0000 (UTC) Received: from fix.fantomatic.co.uk (localhost [127.0.0.1]) by fix.fantomatic.co.uk (8.14.3/8.14.3) with ESMTP id o44IxfNA060393 for ; Tue, 4 May 2010 19:59:41 +0100 (BST) (envelope-from jg@fantomatic.co.uk) Received: (from jpg@localhost) by fix.fantomatic.co.uk (8.14.3/8.14.3/Submit) id o44IxeMg060392 for freebsd-questions@freebsd.org; Tue, 4 May 2010 19:59:40 +0100 (BST) (envelope-from jg@fantomatic.co.uk) X-Authentication-Warning: fix.fantomatic.co.uk: jpg set sender to jg@fantomatic.co.uk using -f Date: Tue, 4 May 2010 19:59:40 +0100 From: Jamie Griffin To: freebsd-questions@freebsd.org Message-ID: <20100504185940.GB60309@fix.fantomatic.co.uk> References: <4BE06C07.4080204@gmail.com> <20100504150605.7725d338@scorpio.seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100504150605.7725d338@scorpio.seibercom.net> X-PGP-Key: 1F50DE41 User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Xorg 7.5, XFCE4 and radeon X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2010 19:59:46 -0000 > I cannot believe that this update was vetted thoroughly, however, it is > a little to late to bitch about it now. These sort of problems are > becoming all to common place lately, IMHO. Feeling your frustration here as well. This latest update has caused a lot of us a great deal of problems: I have no X at all at the moment because of problems with the Intel driver. :-(