Very Computer

I'm having trouble with my font server on RedHat 6.0.  When running
startx, I get an error about not being able to connect to the font server
unix/:-1.

I ran a chkfontpath as per someone else's posting, all the font
directories are there.  If I replace the fontpath statement in XF86Config
with a plain listing of directory entries, X seems to run okay (though any
user but root can't seem to run anything off the KDE menu...).  I've seen
a variety of errors at various points while running X or failing to; most
pertain (as best as I can tell) to the font server.  Looking through
boot.log, I see that xfs started correctly, but when I shut down it
doesn't exit successfully.  This problem suddenly appeared; I don't recall
making any changes to the system between working and not working.

If anyone has any suggestions, please let me know.  I can post a listing
of the errors I've seen if it helps (with some effort...).

Thanks kindly in advance.

--
Ashley Gadd.

Brain:  Promise me something, Pinky.  Never breed.
Pinky:  I'll try.

Quote:>I'm having trouble with my font server on RedHat 6.0.  When running
>startx, I get an error about not being able to connect to the font server
>unix/:-1.

>I ran a chkfontpath as per someone else's posting, all the font
>directories are there.  If I replace the fontpath statement in XF86Config
>with a plain listing of directory entries, X seems to run okay (though any
>user but root can't seem to run anything off the KDE menu...).  I've seen
>a variety of errors at various points while running X or failing to; most
>pertain (as best as I can tell) to the font server.  Looking through
>boot.log, I see that xfs started correctly, but when I shut down it
>doesn't exit successfully.  This problem suddenly appeared; I don't recall
>making any changes to the system between working and not working.

>If anyone has any suggestions, please let me know.  I can post a listing
>of the errors I've seen if it helps (with some effort...).

Error messages are generally pretty helpful. One thing to look for is
full (or nearly full) filesystem, by running 'df'. xfs uses /tmp (maybe
KDE too, dunno), and if filesystem is passed the reserved-for-root
portion, then xfs fails. Something to try anyway.

--
Hal B

--
            Linux helps those who help themselves

Freed up space in /tmp, ran e2fsck and life is good again.