From owner-freebsd-i386@FreeBSD.ORG  Thu Feb 16 21:52:25 2012
Return-Path: <owner-freebsd-i386@FreeBSD.ORG>
Delivered-To: freebsd-i386@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4B154106566C;
	Thu, 16 Feb 2012 21:52:25 +0000 (UTC)
	(envelope-from remko@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 236068FC0C;
	Thu, 16 Feb 2012 21:52:25 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1GLqPC3032148;
	Thu, 16 Feb 2012 21:52:25 GMT
	(envelope-from remko@freefall.freebsd.org)
Received: (from remko@localhost)
	by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1GLqOIL032144;
	Thu, 16 Feb 2012 21:52:24 GMT (envelope-from remko)
Date: Thu, 16 Feb 2012 21:52:24 GMT
Message-Id: <201202162152.q1GLqOIL032144@freefall.freebsd.org>
To: jb.1234abcd@gmail.com, remko@FreeBSD.org, freebsd-i386@FreeBSD.org
From: remko@FreeBSD.org
Cc: 
Subject: Re: i386/165058: xfce4 - startx errors
X-BeenThere: freebsd-i386@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: I386-specific issues for FreeBSD <freebsd-i386.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-i386>
List-Post: <mailto:freebsd-i386@freebsd.org>
List-Help: <mailto:freebsd-i386-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2012 21:52:25 -0000

Synopsis: xfce4 - startx errors

State-Changed-From-To: open->closed
State-Changed-By: remko
State-Changed-When: Thu Feb 16 21:52:24 UTC 2012
State-Changed-Why: 
Ask around on the x11@ mailing list for assistance, this does not seem
like a PR yet. If this is indeed a problem with our infrastructure or a
bug in the OS, please get back to me.

http://www.freebsd.org/cgi/query-pr.cgi?pr=165058