Quote:
Originally posted by FiLiY
Thanks for the link, gave me a better understanding of the font system!
Still having issues with it though. It seems pretty random, sometimes everything is fine other times i load kde up and the fonts look small and thin again.
Seems to have now been isolated to one folder and only getting this error:
Code:
Could not init font path element /usr/X11R6/lib/X11/fonts/local, removing from list!
xset: bad font path element (#64), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
i looked in that folder and there where no fonts there at all. Does anyone know if there is supposed to be fonts there?
I'm going to keep working on this. Any additional help would be appreciated!
Thanks for all your help!
|
First, have you restarted the x server? I'm assuming you have since you've
reloaded KDE.
No fonts in that directory here in Slack-10.0 either. And I did restart the whole box last
night, so my font server is okay - and fwiw it is owned by root on my system. You do
need to run
fc-cache if you've added fonts to your system, but either restarting the X
server, or rebooting (which restarts X), will do this for you. Fc-cache creates an index
of FreeType font files in a directory, but if none are given, each directory is scanned for
font files readable by FreeType. Did you notice that
FontPath "/usr/X11R6/lib/X11/fonts/local/"
is the first one in your /etc/X11/xorg.conf file? So that directory is scanned when X starts.
Now my uneducated suggestion would be to comment (put # in front of) that line in your
/etc/X11/xorg.conf file and see if the error disappears. It will take much more reading
for me to learn if we need that directory. I'll try the same and only post back if I have
negative results.
Another mention is I use Fluxbox, not KDE, so you can be having some specific KDE bug
or error that I wouldn't detect running Flux.
I've read his entire font article (which is very good), but have not gotten as far as actually
changing files - because there are parts of his instructions that are incorrect. This is typical
in my experience with open source documentation. I have been guilty of following instructions
quite verbosely and hosing my system - the last instance being with fcitx.
Therefore, I am reading his article and thoroughly checking my system at the same time. For
example, he says on the
Slackware | Notes page: "Below are notes on using Slackware 10."
Then on the
Slackware | Font Configuration page: "load "freetype" in the modules section of
/etc/X11/XF86Config" but if you'll check Slack-10.0 ->
mingdao@paul:~$ cat /etc/X11/XF86Config
cat: /etc/X11/XF86Config: No such file or directory
The correct file is "/etc/X11/xorg.conf"
You should also Google those three messages and read what you find. This is what I believe:
Directory does not exist or has wrong permissions
<- it exists and permissions are for root
Directory missing fonts.dir
<- it does not have this file, so this could be it
Incorrect font server address or syntax
<- not sure how to check it, but...
mingdao@paul:~$ which xfs
/usr/X11R6/bin/xfs
EDIT: Commenting FontPath "/usr/X11R6/lib/X11/fonts/local/"
out of /etc/X11/xorg.conf seems to have no effect whatsoever on my box.