On Mon, 17 Jan 2000, Paul Sims wrote: ps> I get this problem using xfsft after adding the path to the TTFs in ps> xf86config, reporting an error finding the font "Fixed". Removing the path ps> is ok since the fontpath is defined in the xfsft config file, can't say if ps> thius is the case for xfstt but maybe worth a quick hack to find out ? ps> ps> Kenneth Kellum wrote: ps> > ps> > This is driving me bonkers. I got xfstt working when I was using 6.1. I ps> > decided to install it again to get better fonts with Netscape. ps> > ps> > Here's where I am. ps> > ps> > I put a bunch ot tt fonts in /usr/share/fonts/truetype. ps> > I installed xfstt. ps> > I ran (as root) xfstt --sync and xfstt & before starting X. ps> > In X as root, when I try xset fp+ unix/:7100 ps> > LInux replies ps> > You may want to try changing the port xfstt is using, xfstt no longer uses 7100 to do its work, it now uses 7101. Give that a shot and see what happens. xset fp+ unix/:7101 ps> > xset: bad font path element (#38), possible causes are: ps> > Directory does not exist or has wrong permissions ps> > Directory missing fonts.dir ps> > Incorrect font server address or syntax ps> ps> -- S.Toms - tomas@primenet.com - homepage is in the works SuSE Linux v6.2+ - Kernel 2.2.13 Since we have to speak well of the dead, let's knock them while they're alive. -- John Sloan -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/