Re: vncserver error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tim Waugh <twaugh@xxxxxxxxxx> writes:

>>   $ vncserver
>>   xauth:  error in locking authority file /home/reader/.Xauthority
>>   xauth:  error in locking authority file /home/reader/.Xauthority
>
> What sort of login session is this?  Local console, local X, SSH
> login, su or something else?

Logged in as user reader at console.  Startx from console

User reader runs (from xterm):

 $ vncserver
 (and gets)
  xauth:  /home/reader/.Xauthority not writable, changes will be ignored
  xauth:  error in locking authority file /home/reader/.Xauthority

But I'm noticing now that this is a more general error so something
more is probably wrong here. 

ls -l .Xauthority showed a file owned by root in readers ~/.
sudo rm -f .Xauthority  Then drop to runlevel 3.
Logout completely, log back in

 A simple startx from a fresh login produces a similar error that
output is appended in line at the end of this message.  Also I notice
now there is are these two .Xauthority* files but no plain
.Xauthority.

$ ls -l .Xauth*
-rw-------  2 reader reader 0 Dec 13 07:31 .Xauthority-c
-rw-------  2 reader reader 0 Dec 13 07:31 .Xauthority-l

===
Output from startx log.

cat startx.log
xauth:  error in locking authority file /home/reader/.Xauthority
xauth:  error in locking authority file /home/reader/.Xauthority
xauth:  error in locking authority file /home/reader/.Xauthority
xauth:  error in locking authority file /home/reader/.Xauthority

X Window System Version 6.8.1
Release Date: 17 September 2004
X Protocol Version 11, Revision 0, Release 6.8.1
Build Operating System: Linux 2.6.9-1.751_ELsmp i686 [ELF] 
Current Operating System: Linux reader.local.net0 2.6.9-1.1014_FC4 #1 Fri Dec 3 20:38:05 EST 2004 i686
Build Date: 01 December 2004
Build Host: tweety.build.redhat.com
 
	Before reporting problems, check http://wiki.X.Org
	to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.6.9-1.1014_FC4 (bhcompile@xxxxxxxxxxxxxxxxxxxxx) (gcc version 3.4.3 20041125 (Red Hat 3.4.3-7)) #1 Fri Dec 3 20:38:05 EST 2004 
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 13 07:35:58 2004
(==) Using config file: "/etc/X11/xorg.conf"
(WW) RADEON(0): Failed to set up write-combining range (0xe8000000,0x4000000)
<stdin>:9: invalid preprocessing directive #emacs
<stdin>:17: invalid preprocessing directive ##
<stdin>:24: invalid preprocessing directive ##
<stdin>:29: invalid preprocessing directive ##
<stdin>:30: invalid preprocessing directive ##
<stdin>:31: invalid preprocessing directive ##
<stdin>:32: invalid preprocessing directive ##
<stdin>:35: invalid preprocessing directive ##
<stdin>:37: invalid preprocessing directive ##
<stdin>:38: invalid preprocessing directive ##
<stdin>:52: invalid preprocessing directive #[
<stdin>:73: invalid preprocessing directive ##
<stdin>:74: invalid preprocessing directive ##
<stdin>:75: invalid preprocessing directive ##
<stdin>:76: invalid preprocessing directive ##
<stdin>:77: invalid preprocessing directive ##
<stdin>:78: invalid preprocessing directive ##
<stdin>:79: invalid preprocessing directive ##
<stdin>:80: invalid preprocessing directive ##
xset:  bad font path element (#72), possible causes are:
    Directory does not exist or has wrong permissions
    Directory missing fonts.dir
    Incorrect font server address or syntax
xset:  bad font path element (#72), possible causes are:
    Directory does not exist or has wrong permissions
    Directory missing fonts.dir
    Incorrect font server address or syntax
startkde: Starting up...
kbuildsycoca running...
SetClientVersion: 0 8
<stdin>:479: invalid preprocessing directive #emacs
<stdin>:487: invalid preprocessing directive ##
<stdin>:494: invalid preprocessing directive ##
<stdin>:499: invalid preprocessing directive ##
<stdin>:500: invalid preprocessing directive ##
<stdin>:501: invalid preprocessing directive ##
<stdin>:502: invalid preprocessing directive ##
<stdin>:505: invalid preprocessing directive ##
<stdin>:507: invalid preprocessing directive ##
<stdin>:508: invalid preprocessing directive ##
<stdin>:522: invalid preprocessing directive #[
<stdin>:543: invalid preprocessing directive ##
<stdin>:544: invalid preprocessing directive ##
<stdin>:545: invalid preprocessing directive ##
<stdin>:546: invalid preprocessing directive ##
<stdin>:547: invalid preprocessing directive ##
<stdin>:548: invalid preprocessing directive ##
<stdin>:549: invalid preprocessing directive ##
<stdin>:550: invalid preprocessing directive ##
ALSA lib pcm_hw.c:549:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:549:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:549:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe


[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]