GNOME Bugzilla – Bug 762436
GIMP crashes on MAC Os when loading fonts
Last modified: 2016-09-07 07:58:30 UTC
Gimp crashes and blocked when I start it on MAC Os since 2-3 weeks ago. It blocks during the initialization of the fonts.
It builds the font cache there, this can take a long time.
The problem is not blocking; it crashes with a segfault. Steps to reproduce: 1. Create a new file. 2. Click somewhere on the layer with the font tool 3. Click on the font menu This is on OS X 10.11.3. Here's the command line output after the crash: ---------- (script-fu:66827): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error [1] 66825 bus error gimp ---------- The following warnings/errors are present when I start it with command line (but I could still use it for other purposes): ---------- 2016-03-18 18:34:49.498 gimp[66825:6061031] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead. Error spawning command line 'dbus-launch --autolaunch=a8502bf3924cbd62f940705354d68859 --binary-syntax --close-stderr': Child process exited with code 1 (gimp:66825): GLib-GObject-WARNING **: invalid cast from 'GtkMenuBar' to 'GtkWindow' (gimp:66825): Gtk-CRITICAL **: gtk_window_add_accel_group: assertion 'GTK_IS_WINDOW (window)' failed ---------- Please let me know if you need additional information.
Can you attach a crash report please?
Can not get new version of GIMP to work with recently downloaded Mac OSX 10.11.4 . Older GIMP under 10.8.6 worked. Symptom is that program is "not responding" per the Mac's "Force Quit" utility. Tried both the April and December versions of most recent GIMP. No go...gets to the point of checking for fonts and ends up not responding. Tried GIMP 2.8.14 version also, same results. FYI.
Seems like we got three different people with three different bug descriptions - Matteo's and Matthew's might be the same, though.
The not-responding problem on startup should be fixed in 2.8.18, see bug 449848. I'm tempted to resolve this bug as a duplicate.
Yes I agree, and guys please upgrade to 2.8.18 and report back :)
Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade provided by your Linux distribution. *** This bug has been marked as a duplicate of bug 449848 ***