Date: Thu, 16 Feb 2006 21:49:10 -0500 From: Bob Perry <rperry@gti.net> To: Bob Perry <rperry@gti.net>, freebsd-x11@freebsd.org Subject: Re: Unable to Startx Following Upgrade--Error in, Locking Authority File Message-ID: <43F539A6.5020608@gti.net> In-Reply-To: <20060216055405.GB6213@mail.scottro.net> References: <43F40518.8000003@gti.net> <20060216055405.GB6213@mail.scottro.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Robbins wrote: > -----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. > I need to review .Xauthority and see what it's all about. Hopefully, I'll find the answer soon. Thanks again, Bob Perry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43F539A6.5020608>