After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 794255 - Windows font chache seems broken (does not save/restore properly)
Windows font chache seems broken (does not save/restore properly)
Status: RESOLVED DUPLICATE of bug 782676
Product: GIMP
Classification: Other
Component: General
2.8.22
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2018-03-12 10:29 UTC by Ulrich.Windl
Modified: 2018-03-12 11:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ulrich.Windl 2018-03-12 10:29:15 UTC 
Once working (I cannot exactly remember the version), the font cache in Windows is broken in 2.8.22.
The symptom is that GIMP searches for new fonts every time GIMP is started, and searching for the fonts takes quite some time (if you have a lot of fonts installed). Even when exiting GIMP cleanly, the search for fonts is done again.
So I guess that either the result of font searching is not saved anymore, is not retrieved any more, or the up-to-date state of the cache is not recognized correctly.
The problem was found on multiple machines using Windows 7 (64 bit).
Comment 1 Jehan 2018-03-12 11:24:40 UTC 
Hello,

Thanks for the report. This is most likely a duplicate of bug 782676 which is fixed by bumping the fontconfig requirement, as reproduced and tested by a fontconfig contributor. Unfortunately we haven't released a new version of GIMP with such a newer fontconfig yet, but next 2.8.x release should be fine.

*** This bug has been marked as a duplicate of bug 782676 ***