problem with starting xorg after upgrade

[Scott Robbins]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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. 

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. 


- -- 

Scott

GPG KeyID EB3467D6
( 1B848 077D 66F6 9DB0 FDC2  A409 FA54 D575 EB34 67D6)
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

Xander: I don't like vampires. I'm going to take a stand and say 
they're not good. 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFDvXiJ+lTVdes0Z9YRAgzQAJ9LTJJvcsQt61TcNvW6JP/pBMq7vQCglrs/
B/ZVDFb+N+M0hFbSfDGI1gQ=
=vQUt
-----END PGP SIGNATURE-----