From owner-freebsd-x11@FreeBSD.ORG Thu Feb 16 05:54:08 2006 Return-Path: X-Original-To: freebsd-x11@freebsd.org Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9977216A420 for ; Thu, 16 Feb 2006 05:54:08 +0000 (GMT) (envelope-from scottro@scottro.net) Received: from ms-smtp-03.rdc-nyc.rr.com (ms-smtp-03-smtplb.rdc-nyc.rr.com [24.29.109.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E19D43D49 for ; Thu, 16 Feb 2006 05:54:07 +0000 (GMT) (envelope-from scottro@scottro.net) Received: from mail.scottro.net (cpe-68-175-68-211.nyc.res.rr.com [68.175.68.211]) by ms-smtp-03.rdc-nyc.rr.com (8.13.4/8.13.4) with ESMTP id k1G5p6fh023788; Thu, 16 Feb 2006 00:51:06 -0500 (EST) Received: by mail.scottro.net (Postfix, from userid 1001) id C5D2E5C47; Thu, 16 Feb 2006 00:54:05 -0500 (EST) Date: Thu, 16 Feb 2006 00:54:05 -0500 From: Scott Robbins To: Bob Perry Message-ID: <20060216055405.GB6213@mail.scottro.net> Mail-Followup-To: Bob Perry , freebsd-x11@freebsd.org References: <43F40518.8000003@gti.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <43F40518.8000003@gti.net> User-Agent: mutt-ng/devel-r581 (FreeBSD) X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-x11@freebsd.org Subject: Re: Unable to Startx Following Upgrade--Error in, Locking Authority File X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Feb 2006 05:54:08 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Feb 15, 2006 at 11:52:40PM -0500, Bob Perry wrote: > > Xlib: No protocol specified > > I have no problem running startx as root. I wrote: >> I had a similar problem, although in my case, I suspect it's due to some >> cheap hardware. >> >> At any rate, before starting X try > >> xauth -b quit >> >> This will break any locks. (If your problem has similar causes as mine >> did, there will be an .Xauthority, and a couple of others--.Xauthority-c >> and .Xauthority-l, if I remember correctly.) > > Hi Scott, > I ran the command, xauth -b quit, but no change. You are correct however, in > that two files, .Xauthority-c and .Xauthority-l, were present. Now only > .Xauthority remains. > > Not sure what my next steps are. > > Bob Hrrm, I'm not sure either. The xauth -b quit should remove those two files. It was explained to me on this list that they're lock files that weren't properly removed. Also, I missed that you could run it as root, which means it probably has a different cause. It's probably some silly permissions issue that we're overlooking. - -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Cordelia: Buffy, these men are rich, and I am not being shallow. Think of all the poor people I could help with all my money. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFD9BN9+lTVdes0Z9YRAnNfAKC1aR4UsYPMucAiWYaJGF0swdGd1wCdGnS0 uoQCLbUmFxC9kBM9EuJGfgE= =RH1T -----END PGP SIGNATURE-----