That sounds like the cache version should have been be bumped. Would this warrant a bug report for fontconfig upstream? As I understand, this will reach Ubuntu at some point too, probably around 20.* time frame.
As I understand it, they didn’t bump the cache version because:
- the file format did not change, and
- the file names for UUID and MD5-directory-name based cache files would never collide, due to the different lengths and extra dashes.
Further more, if the 2.13 libfontconfig encountered a read-only directory without a UUID file, it would fall back to checking for an MD5 cache file.
Looking at the 2.13.91 source, it looks like it will also be able to reuse existing valid UUID based cache files, but will attempt to remove UUID files from writeable directories.
So, can you give me some workaround for this issue pls (Arch linux)?
Part of my snap-apps can’t start
user@thinkpad$ libreoffice.writer Fontconfig warning: FcPattern object weight does not accept value [40 210) Application Error
and the other part starts without letters…
code (VSCode) and
telegram work pretty well… Maybe they use some internal fontconfig.
If it is important for anyone in future, here is my solution:
sudo rm /var/cache/fontconfig/* rm ~/.cache/fontconfig/*
Is deleting the font cache the only workaround?