Date: Thu, 5 Jan 2006 21:29:53 +0100 From: Dejan Lesjak <dejan.lesjak@ijs.si> To: freebsd-x11@freebsd.org Subject: Re: problem with starting xorg after upgrade Message-ID: <200601052129.54146.dejan.lesjak@ijs.si> In-Reply-To: <20060105195033.GA8908@uws1.starlofashions.com> References: <20060104152624.GB15636@uws1.starlofashions.com> <200601051632.50625.dejan.lesjak@ijs.si> <20060105195033.GA8908@uws1.starlofashions.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 05 of January 2006 20:50, Scott Robbins wrote: > On Thu, Jan 05, 2006 at 04:32:49PM +0100, Dejan Lesjak wrote: > > On Thursday 05 of January 2006 01:44, Scott Robbins wrote: > > > On Wed, Jan 04, 2006 at 07:19:11PM -0500, Scott Robbins wrote: > > > > > Date: Wed, 04 Jan 2006 15:53:13 +0100 > > > > > > > > > > > AUDIT: Tue Jan 3 20:47:02 2006: 30195 X: client 1 rejected from > > > > > > local host Auth name: MIT-MAGIC-COOKIE-1 ID: -1 > > > > > > > > > > This seems to be the trouble (client would probably be fluxbox or > > > > > twm here). > > > > > > > > As I said in my eariler email, there just seems to be something > > > > peculiar with this machine's onboard via card and X, causing problems > > > > with .Xauthority. > > > > > > > > I reinstalled 6.9 and found that I could eliminate the problem as > > > > long as I removed all .Xauthority files before doing startx. An ugly > > > > hack, but it works. > > > > > > Further addition to this--actually, as long as I remove ~/.Xauthority-l > > > and ~/.Xauthority-c, it works. I don't have to bother removing > > > .Xauthority itself. > > > > That's most probably unrelated problem. > > What seems to happen is that when startx calls xauth to remove tokens > > from ended session, xauth apparently locks Xauthority file (files > > .Xauthority-c and Xauthority-l are used as locks) and then it crashes, > > leaving authority file locked and of course unavailable for next session > > of same user. There might be some error messages about this on terminal > > from which startx was run. > > Yes, it will say, (I thought I mentioned this in my last email) that > there was an error in locking .Xauthority. > > To reiterate, I've always had that problem, but haven't found it > aggravating enough to research deeply. As it only happens on this one > machine, I've always thought it has something to do with the low quality > of the hardware. Quite possible. > > There's probably also a note in dmesg if xauth crashed. Also if you want > > to dig deeper, you could compile xorg with debugging and try to examine > > xauth.core file that you mentioned appears sometimes and file a bug > > report in freedesktop bugzilla if it indeed turns out to be something > > wrong with xauth(1). > > Yes, there is, it just gives the PID and UID; exited on signal 11 (core > dumped). > > As for digging deeper, I really do think the problem is more likely to > be my hardware---again, it's working perfectly on other machines. Signal 11 indeed tends to accompany hardware problems so that might very well be it (you might also want to take a look at http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#SIGNAL11). Thank you for testing and reporting :-) Dejan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601052129.54146.dejan.lesjak>