Solved

could not open default font 'fixed'

Posted on 2000-04-10
10
534 Views
Last Modified: 2013-12-03
I just upgraded a computer from RedHat 6.0 (whose Xserver ran fine) to RedHat 6.2.  After completing the upgrade, X now fails to work.  Xconfigurator runs, correctly identifies the card and monitor, and the test-X it runs works fine.  However, when I actually do startx, the screen blanks, then X stops and I get an error message:

failed to set default font path '/usr/X11R6/lib/X11/fonts/TrueType,unix/:-1'

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

The TrueType directory it refers to did not exist, I created one that was a link to the ttfonts directory in the hopes of making it work.  Otherwise, I haven't done anything to it.  Did some configuration files not get updated?  I'm not sure where to go from here . . .

-Jim
0
Comment
Question by:truittj
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
10 Comments
 

Expert Comment

by:sultrix
ID: 2702439
Ive had a problem like this in the past.

Here are some things you may want to look at if you havn't already.

1) Review your /etc/XF86Config file for     a listing of font paths
2) Make sure all paths listed have a        fonts.alias and a fonts.dir file
3) If those files don't exist use           /usr/X11R6/bin/mkfontdir

I hope this gives you enought to work with.
0
 
LVL 1

Accepted Solution

by:
philiph_elvis earned 150 total points
ID: 2702732
I believe rh6.2 doesn't use the font server any more (xfs).  With rh6.0 and 6.1, the font server program actually makes fonts available.  The config file for this is /etc/X11/fs/config.

Now with rh6.2, I believe the static config files are used.  Check for font path listing in /etc/X11/XF86config.
0
 
LVL 1

Expert Comment

by:Ted22
ID: 2702751
Try reming out # the font path in XF86Config and see if you can startx.
0
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 
LVL 40

Expert Comment

by:jlevie
ID: 2702983
It sounds like you may have installed TrueType font support at some point in the past (probably via freetype or similar). Something in startx or what it invokes is adding the TrueType directory to the font path and when it doesn't exist you get the error. I'd suggest following the process to find where the font path is being modified and removing that definition.
0
 
LVL 3

Expert Comment

by:jyu_88
ID: 2703986
I think there's nothing wrong with XF86Config. It is just xfs (the font server) not running. It is supposed to start by rc2. But, if you are in single user mode using 'startx' to start X,  it will not be there. Try to start it first,
'/etc/rc.d/init.d/xfs start'.

been there done that :-(
0
 
LVL 40

Expert Comment

by:jlevie
ID: 2704222
It probably isn't running, but that would because it thinks it's supposed to serve a font dir that isn't there. My experience is that that'll cause the font server to abort.
0
 
LVL 40

Expert Comment

by:jlevie
ID: 2704244
Look in /etc/X11/fs/config for the line that defines the TrueType font dir and comment it out or delete it. While you're in the file it would "be a good thing" to check the other font dir specifications to make sure that they exist.
0
 
LVL 1

Expert Comment

by:Ted22
ID: 2704605
If you just rem out the font path in XF86Config you can usually startx because it defaults to something. I had a simalar thing happen when I made users conflicting with root and other existing users and xfs would not start. It doesn't solve the problem, but moves you a step closer.
0
 

Author Comment

by:truittj
ID: 2704785
I commented out the bad fontpath lines in /etc/X11/XF86Config and it works now.  Thanks for the extra information on how RedHat 6.2's X is now handling fonts, it was something that I was having trouble figuring out by just reading the config files.

-Jim
0
 

Expert Comment

by:PearlCity
ID: 8818845
For such an error //could not open default font 'fixed'//
even a 'disk space run out' can be a reason


0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I am a long time windows user and for me it is normal to have spaces in directory and file names. Changing to Linux I found myself frustrated when I moved my windows data over to my new Linux computer. The problem occurs when at the command line.…
Little introduction about CP: CP is a command on linux that use to copy files and folder from one location to another location. Example usage of CP as follow: cp /myfoder /pathto/destination/folder/ cp abc.tar.gz /pathto/destination/folder/ab…
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.
Suggested Courses

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question