[SOLVED] xauth/.serverauth issue with startx

This is a full install of slackware64-current logging in to TWM.

I always boot to runlevel 3 then startx from there. When I do I always get a delay with the message:

xauth file /home/rkfb/.serverauth.XXXX does not exist

I can hit Control-C to break it and it'll then load the desktop or if I wait it seems to timeout after a while and then proceed.

Although it was a full install, I did retain my home directory unformatted from the previous slackware64-14.2 install, I don't know if that's relevant at all.

It's not a desperate situation as it's only about a 15 second delay but it's not something I've seen before however and I'm not sure how to resolve it.

Hi, you could try editing your "/usr/bin/startx".

There should be lines in it somewhere which lock like this:

# create a file with auth information for the server. ':0' is a dummy.
    **xserverauthfile=$HOME/.serverauth.$$**
    trap "rm -f '$xserverauthfile'" HUP INT QUIT ILL TRAP KILL BUS TERM
    xauth -q -f "$xserverauthfile" << EOF
add :$dummy . $mcookie
EOF

and change the line **xserverauthfile=$HOME/.serverauth.$$** to **xserverauthfile= `mktemp -p /tmp serverauth.XXXXXXXXXX`**

hope this helps,
Eric.

PS. the ` signs around `mktemp -p /tmp serverauth.XXXXXXXXXX` are the button usually above Tab, not quotes.

Just how many .serverauth.XXXX do you have? I deleted them all to clear that problem and now there are only 2 and no error

I don't get this in Slackware 14.2 but I used to get it regularly in Crux. It has something to do with the xauth procedure used in /usr/bin/startx. Maybe it would be worth comparing the startx script between 14.2 and current.

@Gordie. Crux never deleted stale .serverauth files either. I'm sure the two things are connected.

ericgreenwood123:
$startx
/usr/bin/startx: line 187: /tmp/serverauth.FGf0NoUClh: Permission denied
xauth: file does not exist
xauth: unable to link to authority file , use -n
xauth: timeout in locking authority file /home/rkfb/.Xauthority

Gordie: I have none. I deleted whatever I had when it first started happening thinking it would just regenerate one, but no .serverauth file has ever re-appeared.

Thanks to you both.

Well XFCE and KDE both make them so maybe switch to one of them and login and then switch back to TWM and see if that helps?

You should also check the permissions of /tmp/ to make sure it has the correct permissions. On my 14.2 box, /tmp/ is listed with drwxrwxrwt permissions.

I now have .serverauth.1208 and .serverauth.26614 listed, maybe from logging in to XFCE as suggested. The /tmp permissions match those listed by Bassmadrigal. I still get the error however with a different random number attached each time.

I believe something has gone wrong by me selecting to not format the /home partition during the install (I only formatted / and swap), I was hoping to avoid downloading gigs of files. If I have to I'll just reinstall and format all three, hopefully that should clear it.

no, I do not think formatting may help you.
You may try to use lsof to identify who uses the .serverauth.XXX files.
These files (.serverauth.*) created when you start X, and can be deleted during shutdown (or reboot).

When i made my last post i did not mean typing startx. if you type: sudo nano /usr/bin/startx then it will open the file in the nano text editor and you can edit the lines there.
also what happens if you type sudo startx? because the output text said 'Permission denied.'

Hi, you could try editing your "/usr/bin/startx". There should be lines in it somewhere which lock like this: # create a file with auth information for the server. ':0' is a dummy. **xserverauthfile=$HOME/.serverauth.$$** trap "rm -f '$xserverauthfile'" HUP INT QUIT ILL TRAP KILL BUS TERM xauth -q -f "$xserverauthfile" << EOF add :$dummy . $mcookie EOF and change the line **xserverauthfile=$HOME/.serverauth.$$** to **xserverauthfile= `mktemp -p /tmp serverauth.XXXXXXXXXX`** hope this helps, Eric. PS. the ` signs around `mktemp -p /tmp serverauth.XXXXXXXXXX` are the button usually above Tab, not quotes.

Maybe files in your $HOME are owned by root. You can find out with these commands:

cd
find -uid 0

Then, use chown as root to transfer ownership of these to you as regular user.

ericgreenwood123:
I edited the files in emacs:

startx
/usr/bin/startx: line 187: /tmp/serverauth.WzWWbSGXAD: Permission denied
xauth: file does not exist
xauth: unable to link authority file , use -n
xauth: timeout in locking authority file /home/rkfb/.Xauthority

Didier Spaier: That returns a blank line, sorry.

startx as root however has no issues, it's only as a normal user that I get problems,

try entering this to gain permissions of the file that it is complaining about.

sudo chown youreusername /tmp

Originally Posted by ericgreenwood123 try entering this to gain permissions of the file that it is complaining about. sudo chown youreusername /tmp

You want him to change the owner for the /tmp/ directory?