SoloCDM wrote (in a message from Thursday 6)
> X works perfectly on this system . . .
Which system ? how can you expect to get any useful answer if you give
so little information ? You probably are awere that there exist a
whole bunch of different hardware, operating systems, operating
systems version, software configurations in todays world.
> only X won't load after a
> period of time passes at the console. The following is the results
> of X's dilemma:
>
> _FontTransSocketUNIXConnect: Can't connect: errno = 111
> failed to set default font path 'unix/:-1'
> Fatal server error:
> could not open default font 'fixed'
>
> When reporting a problem related to a server crash, please send
> the full server output, not just the last messages
>
> X connection to :0.0 broken (explicit kill or server shutdown).
Sorry to be rude, but can't you read the X error message you pasted ??
It explicitly says:
+-------------------------------------------------------------------+
| When reporting a problem related to a server crash, please send |
| the full server output, not just the last messages |
+-------------------------------------------------------------------+
So please follow this advice! If you're running XFree86 4.x, you'll
find that output in /var/log/XFree86.0.log. With XFree86 3.3.x you
have to redirect the output of startx to a file with a command like
startx > x.log 2>&1
> How do I get X to allow me to reload the post configurations
> without rebooting?
No one can answer this question given the total lack of information in
your message.
Matthieu
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
