[Fwd: [Fwd: [Fwd: [Fwd: Unable to Startx Following Upgrade--Error in Locking Authority File]]]]

[Bob Perry]

pls disregard; may have overlooked earlier response

Bob

-------- Original Message --------
Subject: [Fwd: [Fwd: [Fwd: Unable to Startx Following Upgrade--Error in 
Locking Authority File]]]
Date: Wed, 15 Feb 2006 22:46:15 -0500
From: Bob Perry <rperry at gti.net>
To: freebsd-x11 at freebsd.org

Re-submitting in the event original was mis-directed.

-------- Original Message --------
Subject: [Fwd: [Fwd: Unable to Startx Following Upgrade--Error in
Locking Authority File]]
Date: Sat, 11 Feb 2006 21:41:15 -0500
From: Bob Perry <rperry at gti.net>
To: x11 at FreeBSD.org

Following upgrade of xorg to version 6.9.0, I have been unable to start
my gnome session.  Following reflects my attempts to resolve via
messages to other mailing lists.

My .xinitrc file reads:
/usr/X11R6/bin/gnome-session

and the gnome-session is listed as:
-r-xr-xr-x  1 root  wheel  107332 Feb  5 23:52  /usr/X11R6/bin/gnome-session


"Hi everyone,
I'm running FreeBSD 5.4-RELEASE #0 and just completed weekly upgrade.
Now when I run "startx", I can not connect to the graphical display
window.  I simply see the gray screen with the small x in the middle.

I went back to the command line to review the text immediately following
the startx command and the first line reads: xauth: creating new
authority file /home/rperry/.serverauth.8414; then, repeated four (4)
times is the following:
    /usr/X11R6/bin/xauth:  error in locking authority file
/home/rperry/.Xauthority
(skip)
    error opening security policy file
/usr/X11R6/lib/X11/xserver/SecurityPolicy
    AUDIT: Sat Jan 28...8433 X: client 1 rejected from local host
    Xlib: connection to ":0.0" refused by server
    Xlib: No protocol specified

I have no problem running startx as root.

cd /home/rperry
ls -l .Xauthority
-rw-------1 root rperry 112 Jan 28 22:13 .Xauthority

Is there a location that lists the error messages like the one I
encountered?  Tried Google and the mailing list archives but wasn't able
to resolve the issue."

One respondent questioned the existence of the .Xauthority file and
suggested I remove it. I did but it returns.

Even access as root is inconsistent. In addition, when I
access via root, the screen resolution is 640 x 480, and it is the only
option available in the desktop screen resolution dialogue box.

Any assistance would be appreciated.

Thanks,
Bob Perry