GNOME Bugzilla – Bug 764830
Startup: loading fonts causes GIMP to become unresponsive
Last modified: 2016-04-10 22:20:48 UTC
I'm having an issue with installing GIMP on my Mac. It comes up to the main loading screen and then when it hits Loading Fonts (May Take A While) the application becomes unresponsive and I cannot proceed. I've tried several times to download and reinstall but still the same issue. I tried older versions but that did not work either. Either the problem would persist or I would be able to open the application but it would not work properly. It was stuck on the Zoom tool and would not let me enter any numbers or letters, instead would use the keyboard shortcuts to zoom in and out of the image. I like using GIMP but have had so many issues with it the past few weeks that I will probably stop using it if I can't resolve it.
We have several complaints about font loading at startup. Depending on the amount of fonts it may take a very long time at first startup. Does this happen only at the first startup? What OS X version are you running? How many fonts are on your system? Because we can handle only one issue per bug report, the issue with the Zoom tool should be handled in a separate bug report. I only found bugs #106913 and #622505 seeming to be related. If they don't cover your issue, please file a new bug.
Does this happen only at the first startup? No, it happens every time I try to use it. What OS X version are you running? Version 10.11.4 How many fonts are on your system? I'm not sure of the total but no more than 10 extra in addition to what the system already comes with. i do not have many extra fonts on the system.
I'm on an older OS X version, but have no issues (expect the delay at first GIMP's startup). We need somebody with that newer version to reproduce and investigate.
Okay let me start it up and let it play out longer. I'll let you know where I'm at
Got it to work, just had to wait a bit longer. For some reason the application reads as not responsive during Fonts and Gradients.
Thanks, in this case, it's another duplicate of 449848. *** This bug has been marked as a duplicate of bug 449848 ***