FS#59889 - [fontconfig] failed to write cache
Attached to Project:
Arch Linux
Opened by bbo2adwuff (bbo2adwuff) - Friday, 31 August 2018, 06:31 GMT
Last edited by Evangelos Foutras (foutrelis) - Monday, 03 September 2018, 20:59 GMT
Opened by bbo2adwuff (bbo2adwuff) - Friday, 31 August 2018, 06:31 GMT
Last edited by Evangelos Foutras (foutrelis) - Monday, 03 September 2018, 20:59 GMT
|
Details
Description:
When updating to the last version fontconfig-1:2.13.1-1 I get following warning: Rebuilding fontconfig cache.../usr/share/fonts/encodings/large: failed to write cache /usr/share/fonts/util: failed to write cache done. When installing another version, i.e. fontconfig-1:2.13.0+15+gc60ed9e-1 I don't get the warning: Rebuilding fontconfig cache... done. |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Monday, 03 September 2018, 20:59 GMT
Reason for closing: Fixed
Additional comments about closing: fontconfig 2:2.13.0+15+gc60ed9e-1 -- if the slowdowns are a separate issue and reappear in a future package, please file a new bug
Monday, 03 September 2018, 20:59 GMT
Reason for closing: Fixed
Additional comments about closing: fontconfig 2:2.13.0+15+gc60ed9e-1 -- if the slowdowns are a separate issue and reappear in a future package, please file a new bug
https://bbs.archlinux.org/viewtopic.php?id=240026
(1/6) upgrading fontconfig [#############################################################################] 100%
Rebuilding fontconfig cache.../usr/share/fonts/encodings/large: failed to write cache
done.
ls -l /usr/share/fonts/encodings/large
total 624
-rw-r--r-- 1 root root 64280 May 31 05:03 big5.eten-0.enc.gz
-rw-r--r-- 1 root root 85154 May 31 05:03 big5hkscs-0.enc.gz
-rw-r--r-- 1 root root 29723 May 31 05:03 cns11643-1.enc.gz
-rw-r--r-- 1 root root 36755 May 31 05:03 cns11643-2.enc.gz
-rw-r--r-- 1 root root 26144 May 31 05:03 cns11643-3.enc.gz
-rw-r--r-- 1 root root 925 May 31 05:03 encodings.dir
-rw-r--r-- 1 root root 140 May 31 05:03 gb18030-0.enc.gz
-rw-r--r-- 1 root root 65442 May 31 05:03 gb18030.2000-0.enc.gz
-rw-r--r-- 1 root root 1664 May 31 05:03 gb18030.2000-1.enc.gz
-rw-r--r-- 1 root root 70451 May 31 05:03 gb2312.1980-0.enc.gz
-rw-r--r-- 1 root root 59047 May 31 05:03 gbk-0.enc.gz
-rw-r--r-- 1 root root 441 May 31 05:03 jisx0201.1976-0.enc.gz
-rw-r--r-- 1 root root 72667 May 31 05:03 jisx0208.1990-0.enc.gz
-rw-r--r-- 1 root root 23831 May 31 05:03 jisx0212.1990-0.enc.gz
-rw-r--r-- 1 root root 34655 May 31 05:03 ksc5601.1987-0.enc.gz
-rw-r--r-- 1 root root 32398 May 31 05:03 ksc5601.1992-3.enc.gz
-rw-r--r-- 1 root root 855 May 31 05:03 sun.unicode.india-0.enc.gz
unlink("/usr/share/fonts/util/.uuid") = 0
stat("/usr/share/fonts/util", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
openat(AT_FDCWD, "/usr/share/fonts/util", O_RDONLY|O_CLOEXEC) = 3
fstatfs(3, {f_type=EXT2_SUPER_MAGIC, f_bsize=4096, f_blocks=10264464, f_bfree=3852494, f_bavail=3325326, f_files=2616320, f_ffree=2245781, f_fsid={val=[1232134085, 1097470473]}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_RELATIME}) = 0
close(3) = 0
openat(AT_FDCWD, "/var/cache/fontconfig/dc9fcae7-af10-4879-81bc-6576285b39e6-le64.cache-7", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=104, ...}) = 0
read(3, "\4\374\2\374\7\0\0\0h\0\0\0\0\0\0\0@\0\0\0\0\0\0\0X\0\0\0\0\0\0\0"..., 64) = 64
close(3) = 0
write(2, "/usr/share/fonts/util: failed to"..., 45/usr/share/fonts/util: failed to write cache
) = 45
sudo SOURCE_DATE_EPOCH=$(date +%s) fc-cache -rs
SOURCE_DATE_EPOCH can also be any positive integer (e.g., 1234).
For me this is only the case for /usr/share/fonts/encodings/large and /usr/share/fonts/utils
(4/7) upgrading lib32-fontconfig [#######################################################] 100%
Rebuilding 32-bit fontconfig cache.../usr/share/fonts/100dpi: failed to write cache
> SOURCE_DATE_EPOCH is used to ensure fc-cache(1) generates files in a deterministic manner in order to support reproducible builds. When set to a numeric representation of UNIX timestamp, fontconfig will prefer this value over using the modification timestamps of the input files in order to identify which cache files require regeneration.
Depending on how you mess with the pseudo-date (try a value *greater than the current time, not less) you will indeed continue to hit the issue regardless.
Rebuilding fontconfig cache.../usr/share/fonts/cyrillic: failed to write cache
/usr/share/fonts/encodings/large: failed to write cache
/usr/share/fonts/misc: failed to write cache
/usr/share/fonts/util: failed to write cache
done.