http://qa.mandrakesoft.com/show_bug.cgi?id=5977


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |INVALID




------- Additional Comments From [EMAIL PROTECTED]  2003-26-09 11:40 -------
It is not needed, fontconfig apps dynamically update their own cache (as user)
if they are not consistent. And each time new fonts are added by a package,
fc-cache is called on the system.

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- 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]
status: RESOLVED
creation_date: 
description: 
In one of my machines, where I ran ML 9.0, then 9.1 and now current cooker,  
I had a longstanding problem with fonts. I could get them to work fine under 
KDE (antialiased fonts), but then Gnome apps and Mozilla had ugly fonts, etc. 
Even DrakConf had ugly fonts. 
 
Long story short. I deleted all the ~/.font* files and I ran fc-cache as a 
normal user, and I fixed most of the problems. Except for DrakConf, that is 
ran as root. Then I deleted /root/.font* and run fc-cache as root and now 
everything is ok. It looks like I had some old crap in these files ruining 
my xfs behavior. 
 
Shouldn't this processed be done automatically by some postinstall script 
after installing fontconfig, a new Xserver o new fonts ?  
 
Also, there was a problem with KDE previews a month ago or so, that was solved 
by running fc-cache as root. fc-cache runs very fast, so it's not an issue to 
include it in post-install scripts IMHO ...

Reply via email to