From owner-freebsd-questions@FreeBSD.ORG Thu Dec 20 09:33:19 2007 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99A5216A417 for ; Thu, 20 Dec 2007 09:33:19 +0000 (UTC) (envelope-from clint@0lsen.net) Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by mx1.freebsd.org (Postfix) with ESMTP id 4629D13C51D for ; Thu, 20 Dec 2007 09:33:19 +0000 (UTC) (envelope-from clint@0lsen.net) Received: from OMTA01.westchester.pa.mail.comcast.net ([76.96.62.11]) by QMTA08.westchester.pa.mail.comcast.net with comcast id SxUM1Y0070EZKEL0500L00; Thu, 20 Dec 2007 09:33:18 +0000 Received: from belle.0lsen.net ([24.20.127.157]) by OMTA01.westchester.pa.mail.comcast.net with comcast id SxZH1Y00F3Pt6RU3M00000; Thu, 20 Dec 2007 09:33:18 +0000 X-Authority-Analysis: v=1.0 c=1 a=5vJcBwrtjk8A:10 a=E5qQiqaLXBc1opfKBA4A:9 a=L3C7Poc0z9ZG2exr5lBpx-JcWnMA:4 a=LY0hPdMaydYA:10 Received: by belle.0lsen.net (Postfix, from userid 1001) id 951F1792DB; Thu, 20 Dec 2007 01:33:17 -0800 (PST) Date: Thu, 20 Dec 2007 01:33:17 -0800 From: Clint Olsen To: questions@freebsd.org Message-ID: <20071220093317.GA20354@0lsen.net> References: <20071220054842.GA1337@0lsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071220054842.GA1337@0lsen.net> User-Agent: Mutt/1.4.2.3i Organization: NULlsen Network X-Disclaimer: Mutt Bites! Cc: Subject: Re: Can't start more than one gnome-session as the same user? 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: Thu, 20 Dec 2007 09:33:19 -0000 On Dec 19, Clint Olsen wrote: > I searched and found a lot of old hits of this error. The solutions are > not very compelling. Unsetting SESSION_MANAGER before launching > vncserver only cascades errors down into the various client programs like > the desktop etc. Answering my own question, the problem is that you really need to start with a fresh shell that isn't inherited from the existing windowing environment. So, logging in remotely and starting up vncserver works. While I wouldn't call this very elegant, at least it works. Thanks, -Clint