Summary: | fc-cache only works without fonts.conf file | ||
---|---|---|---|
Product: | fontconfig | Reporter: | Doug <rickyrockrat> |
Component: | fc-cache | Assignee: | Keith Packard <keithp> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | 2.4 | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 14062 |
Description
Doug
2007-11-18 04:05:58 UTC
Please try 2.5.0 and see if that works; it has new cache validation code that should (I hope) solve the 'failed to write cache' issue. It sure fixes the font cache problem, but it still fails to scan the directory when the fonts.conf file exists. - it just says succeeded. Also, I it give me this message: Fontconfig warning: adding <cachedir>/usr/local/var/cache/fontconfig</cachedir> when I've taken that very line and added it to the fonts.conf. Using strace -e trace=open reveals that it DOES open the /usr/local/etc/fonts/fonts.conf file just prior to giving that warning. It's like it silently fails reading the config somehow. Here's the strace output + the appropriate config file lines. (this is all 2.5.0, btw) open("/usr/local/etc/fonts/fonts.conf", O_RDONLY) = 3 Fontconfig warning: no <cachedir> elements found. Check configuration. Fontconfig warning: adding <cachedir>/usr/local/var/cache/fontconfig</cachedir> .. .. <!-- Font directory list --> <cachedir>/usr/local/var/cache/fontconfig</cachedir> <dir>/usr/local/share/fonts/default</dir> I'm afraid you'll have to debug the library to figure out why it isn't bothering to actually parse the config file. There are a few XML library reasons why no error message would be printed; perhaps there's something amiss there. Please retest with version 2.5 as that has some significant changes in how cache files are written and verified. I'll have to assume that this has been fixed. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.