Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#6024 - fontconfig -- failed to write cache

Attached to Project: Arch Linux
Opened by Rasat (rasat) - Sunday, 17 December 2006, 04:09 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 14 May 2008, 03:04 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Default setting causes "failed to write cache" for all installed fonts. When fonts are poorly configured all apps are slow to load. Fresh install from an install CD, doesn't fail to write cache but all apps are slow when running the newly installed system. When running "fc-cache -f" fails to write again.
This task depends upon

Closed by  Dan McGee (toofishes)
Wednesday, 14 May 2008, 03:04 GMT
Reason for closing:  Works for me
Additional comments about closing:  No responses, "solution" posted
Comment by Jan de Groot (JGC) - Sunday, 17 December 2006, 14:07 GMT
This looks like fontconfig 2.3 configuration with a 2.4 package, which results in all kinds of errors. Check if /etc/fonts/fonts.conf is the configuration file that has been shipped with the 2.4.x package, and not some local-modified version.
Comment by Rasat (rasat) - Sunday, 17 December 2006, 19:47 GMT
> ...not some local-modified version.

I tried different methods: upgrading 2.3, installing a complete fresh setup with latest packages, re-installing only 2.4 by first cleaning up existing files, etc, etc. Doesn't work. When downgrading, everything fine.
Comment by Roman Kyrylych (Romashka) - Tuesday, 06 February 2007, 11:37 GMT
status of the issue?
Comment by Abhishek Dasgupta (abhidg) - Friday, 06 April 2007, 15:12 GMT
This problem might be caused by fc-cache failing to cache because of modification times of the font folders being in the future. A similar problem was reported in Ubuntu and Debian. I could fix this issue on my machine (running 0.8) by just touching all the font folders in /usr/share/fonts, and then running fc-cache.
Comment by arnuld (arnuld) - Wednesday, 16 May 2007, 10:26 GMT
i simply "touch" the directories in "/usr/share/fonts/" and it solves my problem. e.g.

# cd /usr/share/fonts
# touch encodings

:-)
Comment by arnuld (arnuld) - Wednesday, 16 May 2007, 13:20 GMT
this i the link where you can see the problem and solution:

http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/55b64c0f894befbd/bf67c8e620bde0c7?lnk=gst&q=Bug%23387928&rnum=6#bf67c8e620bde0c7

another one:

debian-bugs-dist@lists.debian.org/msg266900.html"> http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg266900.html

Comment by Roman Kyrylych (Romashka) - Thursday, 10 January 2008, 11:24 GMT
Can we close this one, Jan?

Loading...