Re: Unable to Startx Following Upgrade--Error in Locking Authority File
Bob Perry [EMAIL PROTECTED] writes: Not sure if I updated folks on this but the problem persists. (E-mail problems). I've since requested assistance from the gnome and x11 mailing list since the problem started following recent upgrades to those ports. The base system has added some /tmp-cleaning at boot time, specifically to clear out X-related directories. Updating your system to (for example) 6-STABLE may make things work automatically. Alternatively, you could turn on the old /tmp cleaning, which will just wipe the whole directory. If you have a single-user system, the security risks aren't really an issue. Or you could use a memory disk for /tmp. That will (obviously) clear your whole /tmp automatically on a reboot. I do that on my desktops, by setting the tmpmfs and tmpsize variables in rc.conf(5). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to Startx Following Upgrade--Error in Locking Authority File
Lowell Gilbert wrote: Bob Perry [EMAIL PROTECTED] writes: Bingo! It works...but what is a stale authority file and how do you avoid them? Stale is a technical term that means pretty much the same thing it does in your kitchen: something that should've been thrown out before now. I haven't seen one in a long time, so I'm not sure where yours came from, but a system crash might leave one behind. Not sure if I updated folks on this but the problem persists. (E-mail problems). I've since requested assistance from the gnome and x11 mailing list since the problem started following recent upgrades to those ports. Purpose here is to thank you for your assistance if I neglected to do so earlier. Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to Startx Following Upgrade--Error in Locking Authority File
Lowell Gilbert wrote: Bob Perry [EMAIL PROTECTED] writes: 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 (snip) /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 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. Any assistance would be appreciated. Sounds like you have a stale authority file. Try just deleting it before the next time you start up... This is essentially a follow-up to my original issue. I removed the .Xauthority file but it returns and I'm still unable to get into the gnome desktop. Any other suggestions are welcome. thnx, Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to Startx Following Upgrade--Error in Locking Authority File
Bob Perry [EMAIL PROTECTED] writes: 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 FWIW, also had trouble running portupgrade due to repeated timeouts and/or loss of connections. 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. Any assistance would be appreciated. Sounds like you have a stale authority file. Try just deleting it before the next time you start up... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to Startx Following Upgrade--Error in Locking Authority File
Lowell Gilbert wrote: Bob Perry [EMAIL PROTECTED] writes: 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 FWIW, also had trouble running portupgrade due to repeated timeouts and/or loss of connections. 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. Any assistance would be appreciated. Sounds like you have a stale authority file. Try just deleting it before the next time you start up... Bingo! It works...but what is a stale authority file and how do you avoid them? Thnx, Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to Startx Following Upgrade--Error in Locking Authority File
Bob Perry [EMAIL PROTECTED] writes: Bingo! It works...but what is a stale authority file and how do you avoid them? Stale is a technical term that means pretty much the same thing it does in your kitchen: something that should've been thrown out before now. I haven't seen one in a long time, so I'm not sure where yours came from, but a system crash might leave one behind. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to Startx Following Upgrade--Error in Locking Authority File
Lowell Gilbert wrote: Bob Perry [EMAIL PROTECTED] writes: Bingo! It works...but what is a stale authority file and how do you avoid them? Stale is a technical term that means pretty much the same thing it does in your kitchen: something that should've been thrown out before now. I haven't seen one in a long time, so I'm not sure where yours came from, but a system crash might leave one behind. This is getting curiouser and curiouser. As mentioned, I was able to access my GNOME display but noticed that the screen resolution was 640x480. As a matter of fact, it was the only option available when I tried to change it in the GNOME screen resolution dialogue box. While troubleshooting the issue, I was surprised when I ran startx again and encountered the very same error which prevented me from gaining access to the GNOME desktop originally. Any ideas for next steps? Thnx, Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Unable to Startx Following Upgrade--Error in Locking Authority File
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 FWIW, also had trouble running portupgrade due to repeated timeouts and/or loss of connections. 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. Any assistance would be appreciated. Thanks, Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
