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 156672 - Browsing fonts makes Gimp crash
Browsing fonts makes Gimp crash
Status: RESOLVED DUPLICATE of bug 154144
Product: GIMP
Classification: Other
Component: General
2.0.x
Other Mac OS
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
: 157956 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-10-28 09:21 UTC by Sébastien Pierre
Modified: 2004-11-17 00:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sébastien Pierre 2004-10-28 09:21:02 UTC
On MacOSX, with gimp-app.sf.net version of Gimp (2.0.5), with the text tool,
Gimp crashes when I'm browsing the fonts.

I can browse some fonts, but when I select the first fonts of the drop-down
list, Gimp repeateadly crashed, while I would be able to browse and select fonts
that were below the currently selected fonts.

I guess there is a problem in rendering the fonts (maybe related to freetype or
pango)...
Comment 1 Sven Neumann 2004-10-28 09:42:53 UTC
This is usually caused by broken fonts and old freetype libraries.
Comment 2 Sven Neumann 2004-10-28 09:47:17 UTC
Can you please report this problem at the gimp-app.sf.net bug-tracker and ask
Aaron to update freetype in his GIMP build? I would suggest we close this report
as NOTGNOME then and add a link to the report in the sf bugtracker.
Comment 3 Sébastien Pierre 2004-10-28 09:56:27 UTC
Sure, I will tell this to Aaron. However, I tried with the latest Fink
(fink.sf.net) version of Gimp-2, which has the latest freetype2, and the bug
does still occur.... I should add that browsing fonts is painfully slow...

Here is the crash log I get:

(gap_wr_opacity:29506): LibGimp-CRITICAL **: file gimp.c: line 549
(gimp_install_procedure): assertion `(n_return_vals == 0 && return_vals == NULL)
|| (n_return_vals > 0 && return_vals != NULL)' failed

(gimp-2.0:29441): GLib-GObject-CRITICAL **: file gobject.c: line 1561
(g_object_ref): assertion `G_IS_OBJECT (object)' failed

** (gimp-2.0:29441): CRITICAL **: file pango-engine.c: line 68
(_pango_engine_shape_shape): assertion `PANGO_IS_FONT (font)' failed
/sw/bin/gimp-2.0: fatal error: file shape.c: line 75 (pango_shape): assertion
failed: (glyphs->num_glyphs > 0)
(script-fu:29619): LibGimpBase-WARNING **: script-fu: wire_read(): er


Seems like Pango has a problem witha particular fonts... which are all MacOS X
standard fonts...
Comment 4 Sven Neumann 2004-10-28 10:06:47 UTC
It would be interesting to get a stack trace from the point where the first
warning (not the one from gap_wr_opacity, that one is unrelated) occurs. Guess I
need to do some debugging on a Mac...
Comment 5 Brion Vibber 2004-11-01 04:28:19 UTC
The fatal font seems to be "GB18030 Bitmap":
-rw-rw-r--    1 root     admin     7107888 Sep 12  2003 /Library/Fonts/NISC18030.ttf

$ md5sum /Library/Fonts/NISC18030.ttf 
49ed9a43f443daa9b289db5d2e3f20c1  /Library/Fonts/NISC18030.ttf

The same font file seems to be included in the OpenOffice 1.1.2 distribution.
Comment 6 Brion Vibber 2004-11-01 05:44:17 UTC
Not actually in OpenOffice; that's just a copy of all my font files that OpenOffice has helpfully made for 
its own nefarious purposes. Sigh.
Comment 7 Brion Vibber 2004-11-01 07:19:43 UTC
Fink doesn't normally provide a freetype2 library, preferring to let things link against the system copy 
in /usr/X11R6/lib.

Running Gimp 2.1 with DYLD_LIBRARY_PATH set to the dir where I'd installed an updated freetype 
(2.1.9) and pango (1.6.0), it doesn't die on GB18030 Bitmap, whereas it does die if I don't set the 
DYLD_LIBRARY_PATH, presumably picking up the system Freetype instead.

My quick DYLD_LIBRARY_PATH tests fail with unresolved symbols for my already-compiled gimp 2.0; it 
may be necessary to recompile things.
Comment 8 roncerito 2004-11-07 17:08:35 UTC
I have the same problem running Gimp.app (2.0.5-2). My error log is the same as Sebastién's (see 
below). It seems Pango-related. Now version 2.0.6 offers a resolution to another Pango-related bug
- <a href="http://bugzilla.gnome.org/show_bug.cgi?id=154144">bugzilla #154144</a> - which 
IMHO seems to strongly resemble the one described here.


Q. Can we classify this bug as a duplicate of #154144?

Q. Until Aaron packages 2.0.6, is there a way to circumvent the problem? 

Brion - have you positively identified a specific font - /Library/Fonts/NISC18030.ttf ? 
Do you think removing the offending font from your /Library/Fonts folder would work as a temporary 
solution? 

- - - - - - -
My Console error log:

(gimp-2.0:467): GLib-GObject-CRITICAL **: file gobject.c: line 1561 (g_object_ref): assertion 
`G_IS_OBJECT (object)' failed

** (gimp-2.0:467): CRITICAL **: file pango-engine.c: line 68 (_pango_engine_shape_shape): assertion 
`PANGO_IS_FONT (font)' failed
/Volumes/Applications/Gimp/Gimp.app/Contents/Resources/bin/gimp-2.0: fatal error: file shape.c: 
line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0)

(script-fu:500): LibGimpBase-WARNING **: script-fu: wire_read(): error
Comment 9 Sven Neumann 2004-11-07 17:36:11 UTC
If it is a duplicate of bug #154144 then you can easily fix it by updating to
Pango 1.4 or 1.6.
Comment 10 Sven Neumann 2004-11-10 10:52:12 UTC
It would be important to get some feedback here whether upgrading to a nwever
version of Pango fixes the problem or not. Marking as NEEDINFO.
Comment 11 Sven Neumann 2004-11-11 16:42:47 UTC
*** Bug 157956 has been marked as a duplicate of this bug. ***
Comment 12 Manish Singh 2004-11-17 00:12:18 UTC
With current GIMP 2.0.x CVS and pango 1.2.5 on linux, I can't get it to crash at
all with that font (including rendering a chinese glyph to the canvas).
Reverting the patch in #154144 makes things crash with that font.

I'm going to close this as a duplicate of #154144.
Comment 13 Manish Singh 2004-11-17 00:12:40 UTC

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