Thank you for your detailed message.. unfortunately it did not help.  What 
I have been able to figure out.. this problem occurs ONLY on one specific 
machine.. I installed it on another desktop, and it comes up properly 
using the /etc/sysconfig/vncservers method.. It also doesn't occur with a 
Fedora Core 3 Test 3 installation on my laptop.

When I do start it on the machine having difficulties, I get the follow 
information in my VNC log:

<-- Text Below -->

_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be 
created.
_XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, errno = 
2
_XSERVTransMakeAllCOTSServerListeners: failed to create listener for local

Xvnc version 4.0 - built Oct  6 2004 08:11:33
Underlying X server release 60801000, The X.Org Foundation


Fri Nov 12 21:44:22 2004
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on port 5902
 vncext:      Listening for HTTP connections on port 5802
 vncext:      created VNC server for screen 0
error opening security policy file 
/usr/X11R6/lib/X11/xserver/SecurityPolicy
Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing 
from li
st!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing 
from li
st!

<-- Text Above -->

Those first 3 lines are what have me concerned and I think ultimately the 
problem.  Its having trouble creating a lockfile or socket file or 
somekind as far as I can tell.

If I kill that session, and restart MANUALLY after rebooting, I do not get 
those 3 lines and the Gnome session comes up properly.  So there is 
something happening at boot which is not allowing this session to come up 
fully.

Thats what is driving me crazy, it will start with the EXACT same settings 
if I simply do it from the command line after boot.

Thanks,
Ronald Hall
[EMAIL PROTECTED]
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to