[Fontconfig] Re: Crash when non-existing directories are referenced in ~/.fonts.cache

Patrick Lam plam at MIT.EDU
Mon Jan 30 08:03:53 PST 2006

Matthias Clasen wrote:
> Well, the current state of continuous recreation of $HOME/.fonts.cache
> is certainly worse than having to run fc-cache after font installation. 
> fc-cache does not have to be run as root, I can use it just fine as an
> ordinary user to create a font cache in $HOME/.fonts.

Yes.  However, that cache is just a cache for the .fonts directory, not 
for the system fonts.

> But regardless of this discussion, I'm still seeing some problems with
> current CVS. Repeatedly running fc-list : makes $HOME/.fonts.cache-2
> change its size (for me it oscillates between 141434 and 141538), so 
> it is obviously being rewritten every time, even though the set of 
> installed fonts does not change at all.
> fc-cat does not list any fonts when run on $HOME/.fonts.cache-2.
> When run on one of the directory caches in /var/cache/fontconfig, it
> produces garbage in the charset fields.

I've fixed the fc-cat bug for the global cache.  I haven't observed any 
garbage in fc-cat on charset fields.  Currently fontconfig isn't 
properly reading the global cache, so I'm taking a look at this.


More information about the Fontconfig mailing list