gauge73

[Log in to get rid of this advertisement]

Whenever I run vncserver (except as root), I get the following error message:

xauth: timeout in locking authority file /root/Xauthority

I get it twice and then VNC starts working.



I'm taking a UNIX class at school, so I started fooling around with this and I determined that in the vncserver executable (which is a perl script), the associative array element $ENV{XAUTHORITY} is evaluating to /root/.Xauthority. I have no idea why this is or how I can change it. Here is the line that evaluates that elemen in the vncserver script:

$xauthorityFile = "$ENV{XAUTHORITY}" || "$ENV{HOME}/.Xauthority";

I supposed I could take the first command out and just leave it at "$ENV{HOME}/.Xauthority", but I would prefer to figure out why $ENV{XAUTHORITY} is evaluating to /root/.Xauthority. Could anyone shed any light on the matter?

gauge73

For what information it is worth, I just changed the line to the following:

$xauthorityFile = "ENV{HOME}/.Xauthority";

I no longer get the error, but when VNC starts I don't get KDE anymore. I just get a blank X background. Perhaps the $xauthorityFile variable is supposed to be /root/.Xauthority and the error is elsewhere?

** Side Question ** - If you have an empty X environment (no windows/shells open), how can you open a new shell to work with?

david_ross

Take a look at the startup script in your ~/.vnc directory and post its contents.

You can start a program on an X display by setting the dispaly variable then running a gui command:
export DISPLAY="ip.of.x.server:X"
where X is the display number
then run your app - eg:
xterm

gauge73

$ cat xstartup
#!/bin/sh

[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
startkde


That side question from earlier still stands... how do I open a new window to work with when I'm sitting at a blank X environment?

david_ross

You need to switch back to a console first and run the commands there to open the required window.

Try changing that file to:
#!/bin/bash
xterm &
startkde &

make a backup first!

gauge73

I got the same result. I have it running sh instead of bash, but I assume that doesn't matter.

Thanks for the help. What should I try next?

david_ross

Is the service listeng ok - post the output of:
netstat -nlp

gauge73

Just FYI, in case I didn't make it clear, I can connect to VNC and it works fine. I just get those error messages and have to wait for the timeouts every time I start the server. After that it's fine.


OUTPUT:

$ netstat -nlp
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:32768 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:32769 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:5801 0.0.0.0:* LISTEN 5375/Xvnc
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN 5375/Xvnc
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:6001 0.0.0.0:* LISTEN 5375/Xvnc
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN -
udp 0 0 0.0.0.0:32768 0.0.0.0:* -
udp 0 0 127.0.0.1:32770 0.0.0.0:* -
udp 0 0 192.168.1.2:137 0.0.0.0:* -
udp 0 0 0.0.0.0:137 0.0.0.0:* -
udp 0 0 192.168.1.2:138 0.0.0.0:* -
udp 0 0 0.0.0.0:138 0.0.0.0:* -
udp 0 0 0.0.0.0:968 0.0.0.0:* -
udp 0 0 0.0.0.0:111 0.0.0.0:* -
udp 0 0 0.0.0.0:631 0.0.0.0:* -
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node PID/Program name Path
unix 2 [ ACC ] STREAM LISTENING 4530 - /tmp/.iroha_unix/IROHA
unix 2 [ ACC ] STREAM LISTENING 11246 5448/kdeinit: Runni /tmp/ksocket-gauge/kdeinit-:1
unix 2 [ ACC ] STREAM LISTENING 9631 - /tmp/ssh-XX3MB38i/agent.4981
unix 2 [ ACC ] STREAM LISTENING 4774 - /tmp/.gdm_socket
unix 2 [ ACC ] STREAM LISTENING 11597 5547/evolution /tmp/orbit-gauge/orb-389413134772397593
unix 2 [ ACC ] STREAM LISTENING 10169 - /tmp/mcop-root/localhost_localdomain-13f9-3fcae707
unix 2 [ ACC ] STREAM LISTENING 10049 - /tmp/ksocket-root/kdeinit-:0
unix 2 [ ACC ] STREAM LISTENING 11276 5454/kdeinit: klaun /tmp/ksocket-gauge/klauncherFgCJOa.slave-socket
unix 2 [ ACC ] STREAM LISTENING 11607 5550/oafd /tmp/orbit-gauge/orb-12770057631546741199
unix 2 [ ACC ] STREAM LISTENING 11900 5602/wombat /tmp/orbit-gauge/orb-9442569731093555590
unix 2 [ ACC ] STREAM LISTENING 11648 5558/bonobo-moniker /tmp/orbit-gauge/orb-12750223671745105558
unix 2 [ ACC ] STREAM LISTENING 11673 5562/evolution-mail /tmp/orbit-gauge/orb-10915013861240847110
unix 2 [ ACC ] STREAM LISTENING 11684 5564/gconfd-1 /tmp/orbit-gauge/orb-19015563951909935362
unix 2 [ ACC ] STREAM LISTENING 11728 5571/evolution-addr /tmp/orbit-gauge/orb-901634171931801804
unix 2 [ ACC ] STREAM LISTENING 11752 5575/evolution-cale /tmp/orbit-gauge/orb-711169873625217233
unix 2 [ ACC ] STREAM LISTENING 11776 5580/evolution-alar /tmp/orbit-gauge/orb-11200818062128150885
unix 2 [ ACC ] STREAM LISTENING 11801 5582/evolution-exec /tmp/orbit-gauge/orb-537955297239337992
unix 2 [ ACC ] STREAM LISTENING 4474 - /dev/gpmctl
unix 2 [ ACC ] STREAM LISTENING 4654 - /tmp/.font-unix/fs7100
unix 2 [ ACC ] STREAM LISTENING 4784 - /tmp/.X11-unix/X0
unix 2 [ ACC ] STREAM LISTENING 10816 5375/Xvnc /tmp/.X11-unix/X1
unix 2 [ ACC ] STREAM LISTENING 10054 - /tmp/.ICE-unix/dcop5096-1070262016
unix 2 [ ACC ] STREAM LISTENING 10200 - /tmp/.ICE-unix/5125
unix 2 [ ACC ] STREAM LISTENING 11253 5451/kdeinit: dcops /tmp/.ICE-unix/dcop5451-1070262448
unix 2 [ ACC ] STREAM LISTENING 11406 5474/kdeinit: ksmse /tmp/.ICE-unix/5474
unix 2 [ ACC ] STREAM LISTENING 10077 - /tmp/ksocket-root/klauncherQOrS0b.slave-socket

david_ross

Sorry - I had misunderstood. Can you post the output as it appears when you start the server.

gauge73

$ vncserver -geometry 1280x1024
xauth: timeout in locking authority file /root/.Xauthority
xauth: timeout in locking authority file /root/.Xauthority

New 'X' desktop is localhost.localdomain:1

Starting applications specified in /home/gauge/.vnc/xstartup
Log file is /home/gauge/.vnc/localhost.localdomain:1.log

$


There is a long pause before each of the xauth: timeout lines. What should I do?

gauge73

*bump*

gauge73

*bump*

Pleeeez help? :x

netkepala

Dear Gauge73,

I get the same timeout error msg when I started using RH Linux 9.

When I was using RH Linux 7.x there was no such error. I am using the same rpm file from the tightvnc website

I suspect there are some changes to the OS which caused this problem. Any guru be able to help us ??

Thanking very much in advance

samiline

I think you are not the owner of /home/gauge or you don;t have permission on /home/gauge