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 796363 - GIMP No Longer Works After GIMP 2.10 debacle
GIMP No Longer Works After GIMP 2.10 debacle
Status: RESOLVED DUPLICATE of bug 782676
Product: GIMP
Classification: Other
Component: General
gimp-2-8
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2018-05-23 17:28 UTC by RMF Runyan
Modified: 2018-05-23 18:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description RMF Runyan 2018-05-23 17:28:18 UTC 
Now GIMP no longer works on my system.

I installed GIMP 2.8.22 and now it gets stuck on looking for fonts.  I know this is an ongoing issue which y'all just cannot seem to solve.  However, should it be taking more than 10 minutes to find fonts?

Perhaps y'all need to look into how Photoshop does it.  PS starts up about four times faster than GIMP.

rmfr
Comment 1 Kunda 2018-05-23 18:17:07 UTC 
please add your gimp -v info
Comment 2 Jehan 2018-05-23 18:26:34 UTC 
Also please install GIMP 2.10. There is a known bug in fontconfig which made font loading even longer than it should be and I believe we have not made a single GIMP 2.8.x release with a newer fontconfig fixing this bug.

Actually fontconfig installed with GIMP version 2.8.22 even had a nasty rebirth of this issue. See bug 782676.

GIMP 2.10.0 is the first release with a fixed fontconfig, so it is not astonishing that you get the issue with GIMP 2.8.22.

Now there are still improvements to be done, and we have bug 788810 for this.

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