4 ms·
Yeah, you most likely got rid of an existing cache, which couldn't be updated due to file locking. That issue is fixed in recent versions of the fontconfig libr
by schumaml 9y ago
Yeah, you most likely got rid of an existing cache, which couldn't be updated due to file locking. That issue is fixed in recent versions of the fontconfig library.
A fairly current one is shipped with the 2.9.6 installer, so many of the infamous issues should be gone.