Font problem in X "could not open default font 'fixed'"

[Giscardo]

I just installed the latest version of X on my computer (I don't have any window managers yet), on slackware 8.0 using a Geforce2MX. Whenever i start x using either "startx" or "XFree86" i get the following error:

Fatal server error:
could not open default font 'fixed'

I have a bunch of fonts installed under /usr/X11R6/lib/fonts in various folders. When i typed 'XFree86 -xf86config /root/XF86config.net' for the first time X actually started in 800x600 resolution, so I at least know that X somewhat works.

[danrees]

I had the same problem with Mandrake - you need to go into /etc/X11/XF86Config (XF86Config-4 if you're using XFree86 4.0.3), and add some font paths. There should be one at least already probably:

FontPath "unix/:-1x"

Then add all your font directories underneath that (they're probably in /usr/X11R6/lib/X11/fonts), so:

FontPath "/usr/X11R6/lib/X11/fonts/100dpi"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
....
....

Then save and startx. Things should be fine.

[wittysaint]

You dont have to add the font paths if you have the line FontPath "unix/:-1" (which indicates that ur font needs are being handled by xfs and the no. indicates the port on which the unix daemon will be running).
check in ur xfs config file(usually at /etc/X11/fs/config).check the line catalogue.check to c whether location specified as having font files actually have them.
if ur running RH 7.0 or higher that fontpath line in XF86Config shd be
FontPath "unix/:7100"
HTH

[danrees]

My mistake, that's how I got things working, but if that's the correct way, then I might just try that. :)

[danrees]

No wonder it wasn't working! I had:
unix:-1x instead of unix:-1! Must have been a typo when I was editing :rolleyes:!

Everything's working out of /etc/X11/fs/config now. :cool:

[ 05 August 2001: Message edited by: danrees ]

[Giscardo]

danrees, your suggestion worked. Thanks!

[danrees]

Wittysaint's solution is the more elegant one, but if it works, then don't fix it! ;) (Although I have changed my setup to the one proposed by Wittsaint once I realised my typo error!)