help! /home/tc created root:root -- stuck waiting on .Xauthority

[kevinfish]

I added persistent home with home=sda7 in my menu.lst file, removed home/tc from .filetool.lst and now every time it boots ~tc is created with root:root ownership and it gets stuck with:

xauth: timeout in locking authority file /home/tc/.Xauthority

I have to break out with ^C, type:

$ sudo chown tc:staff ~tc; startx

to get it all running again.  I have checked there are no other mydata.tgz files on the system and one I have doesn't have home/tc in it.

Why is it doing this?

P.S. also check my other posts because the problems may be related.

[curaga]

Is this a fat filesystem?

[kevinfish]

no

[Guy]

This is strange, and shouldn't happen. I think it is a matter of considering any possible causes, and eliminating the ones you know are not causing it.

What filesystem is it?

If you save files in /home/tc, are they still there next time you boot?

What other boot options are you using?

Does it still happen if you boot with the norestore boot option?

Is there anything unusual about your installation which may cause it to function differently to a normal one?

[kevinfish]

ext3

yes, persistent /home

kernel /bzImage quiet xvesa=1280x800x16 laptop waitusb=5 root=/dev/ram0 real_ro
ot=/dev/sda7 max_loop=255 home=sda7 tce=sda7 opt=sda7

haven't checked the norestore option (but since I'm not backing up /home/tc I don't see what difference it should make -- but I'll try it anyway).

not that I can think of right off the bat.  I have a multi-boot with gentoo but I haven't even booted it in a long time.

[robc]

I started getting this error too. It started happening when I decided to add some files from home/tc to my backup.

I ended up adding `chown -R tc:staff /home/tc` to bootlocal.sh. This may be a problem with an extension that is loaded. You can try booting with just 'norestore' or just 'base' to verify where the permissions errors are coming from.

[kevinfish]

I'm not currently using a usb/cf disk so I doubt it is the waitusb thing.  I tried the norestore and my ~tc was still root:root.  I put the chown thing in my bootlocal.sh and it still has the same error (although I didn't use the recursive flag, just the chown on the ~tc dir -- I'll try that next).

[kevinfish]

as an afterthought, if I'm using a persistent home it must not be actually creating ~tc, right?  So something is actively chowning it to root:root IMHO.

[Guy]

If it is an extension, it is good to know so the extension can be fixed.

You can boot with base and see if it happens.

If it is, temporarily remove various extensions until you find out which one it is.

Report it to the person who made the extension.

[Pats]

Corrupted filesystem or corrupted grub ?
Why you do not try TC on a FAT pertition to see if the ext3 fs is giving these hiccup ?
Or may be a fresh install on a fresh formated HDD / PenDrive ?
Just a thought !
~ Pats

[Pats]

On the second thought, can the culprit be your bootcodes :
root=/dev/ram0 and/or real_root=/dev/hda7 ?
Try to remove both, and try only root=/dev/hda7 - to check the result.
Hope this helps !

~ Pats

[kevinfish]

as per my other posts, I re-installed with 2.10 and the problem went away.  Go figger?!? 

[MikeLockmoore]

I started getting this in my 2.9 installation too.  I then tried a 2.10 version install, but the problem did _NOT_ go away for me.  And I am pretty stumped about why we would be getting this.  

BTW, this is occurring in the frugally-installed version of TC in my eeePC nettop.
--
Mike

[MikeLockmoore]

Update: I cleared out my TCE directory and installed all my regular extensions from the beginning under 2.10.  Now I don't have any problem xauth problems at all.  Looks like something got messed up in my 2.9 extension set that was not resolved until I made a fresh start.  Now 2.10 is working pretty well for me.

Oh, by way, I've added ALSA master sound control support to Flit.  It may need some more work before I release it to the public, but its nice to have it now with ALSA (which I use with Skype).
--
Mike L.

[roberts]

Glad to hear it is working. Looking forward to an update for flit.