Mailinglist Archive: opensuse (3394 mails)
|< Previous||Next >|
Re: [SLE] xfsft not working - Help!!!!
- From: abrahams@xxxxxxxxxxx (Paul W. Abrahams)
- Date: Tue, 07 Mar 2000 17:59:23 -0500
- Message-id: <38C589CB.8672F692@xxxxxxxxxxx>
George Zeigler wrote:
> > > When I do startx I get the error
> > > "Fatal server error: could not open default font 'fixed'". At the very
> > > bottom, I list all the files in my directory /usr/X11R6/lib/X11/fonts/TrueType
> > >
> > > Any ideas?
> > I've seen that error also.
> Yeah, it's all over Deja, but could not find a solution.
> > I believe the Font Howto mentions some command you can use to check
> > what your fontpath is. I'd suggest, as an experiment, that you reorder the items in XF86Config
> > so that the unix one comes last
> I even tried uncommenting every Type 1 path, leaving only the path
> FontPath "tcp/localhost:7101"
Try reversing that: comment out the tcp/localhost path and leave the rest uncommented. You should
then be able to start X, but without any TrueType fonts. That will verify that the problem is
entirely in the configuration for tcp/localhost:7101.
> > (or at least after the unscaled ones) and then start fiddling.
> > The likely cause, as I remember, is either a missing directory in the xfs configuration file or a
> > directory without the fonts.dir or fonts.scale file. The default location for the xfs
> > configuration is
> > /usr/X11R6/lib/X11/fs/config
> > which you can determine for yourself by typing:
> > strings `which xfs` | grep config
> Here is what I got:
> root@host-name:/usr/X11R6/lib/X11/fonts > strings `which xfs` | grep config
> fatal: couldn't read config file
> couldn't read config file
> Re-reading config file
> couldn't parse config file
> usage: %s [-config config_file] [-port tcp_port]
> CONFIG: error reading configuration file "%s"
> CONFIG: can't open configuration file "%s"
> CONFIG: insufficient memory to load configuration file "%s"
> What does this mean?
Those are all the text strings within xfs that contain the substring `config'. The apparent error
messages aren't error messages as far as you're concerned; they're just strings containing `config'.
The only interesting line is the first one, which tells you where the config file is. Have a look at
it, and look at the xfs man page to interpret it. The trouble almost certainly lies within that file.
Like the man said, ``intuitively obvious to the most casual observer'' <s>.
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
|< Previous||Next >|