https://qa.mandrakesoft.com/show_bug.cgi?id=812
------- Additional Comments From [EMAIL PROTECTED] 2003-01-24 06:18 ------- fontconfig-2.1-5mdk still has the same problem. After installing it, the sequence cd /usr/X11R6/lib/fonts fc-cache -v mv drakfonts .. made gedit work, and then, mv ../drakfonts . cd drakfonts fc-cache -f -v `pwd` made gedit again functional. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] description: If you run fc-cache in /usr/X11R6/lib/X11/fonts it will examine all subdirs and make a cache. And then if you run (say) gedit, you will see, [root@localhost fonts]# gedit No fonts found; this probably means that the fontconfig library is not correctly configured. You may need to edit the fonts.conf configuration file. More information about fontconfig can be found in the fontconfig(3) manual page and on http://fontconfig.org To fix, [root@localhost fonts]# cd drakfont/ [root@localhost drakfont]# fc-cache -v -f `pwd` fc-cache: "/usr/X11R6/lib/X11/fonts/drakfont": caching, 348 fonts, 0 dirs fc-cache: succeeded [root@localhost drakfont]# gedit [root@localhost drakfont]# also, mv drakfont ..; gedit, works sometimes. The generated cache files are identical inside the drakfont directory. It is not related to what fonts you have. I think it is probably the timestamp on the font-cache file in the parent directory. In the case that it fails, gedit takes a long time to start up (10 seconsd, say) and there's lots of disk access. In the case it works, it is fast.
