<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - fontconfig cache creation takes a long time during GIMP startup" href="https://bugs.freedesktop.org/show_bug.cgi?id=101820#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - fontconfig cache creation takes a long time during GIMP startup" href="https://bugs.freedesktop.org/show_bug.cgi?id=101820">bug 101820</a> from <a class="email" href="mailto:eduard.braun2@gmx.de" title="Eduard Braun <eduard.braun2@gmx.de>"> Eduard Braun</a> <pre>We have exactly the same problem in Inkscape for Windows. We could resolve one issue we faced [1]: By default fontconfig stored the cache to a temporary location. If this temporary location was cleared (i.e. by some system cleanup tool) the cache had to be re-created the next time Inkscape was run. (Maybe something like this is causing some of the "every time" comments for you?) We fixed the issue by configuring fontcache to write the cache to LOCAL_APPDATA_FONTCONFIG_CACHE We still have the underlying issue [2]: Creation of the fontconfig cache needs time, especially on slower systems or systems with a lot of fonts installed. This delays the startup of Inkscape considerably, which is especially bad since it obviously affects every first time user (and even worse because Inkscape - in contrast to GIMP - does not have a startup screen informing the user about what it's doing. Subsequent startups with this configuration are usually fast though, with the exception of <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Cache file update fails on Windows (also Cygwin)" href="show_bug.cgi?id=99360">bug 99360</a> which lately prevented fontconfig to update an outdated cache file. The behavior matches what you experience: a .new file with the updated cache was created but never used to actually replace the old cache (this was due to file locks as described in the linked bug; the patch there fixed the issue for us, though). [1] <a href="https://bugs.launchpad.net/inkscape/+bug/1196373">https://bugs.launchpad.net/inkscape/+bug/1196373</a> [2] <a href="https://bugs.launchpad.net/inkscape/+bug/1528629">https://bugs.launchpad.net/inkscape/+bug/1528629</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>