#1436 freetype219, gimp-2.0 crash when accessing fonts

[Sam Halliday]

Hello,

I have been unable to use fonts within the Fink build of gimp-2.0 for a long time and after an update to the latest versions of everything in the unstable branch, I finally decided to report this as a bug. A backtrace hints that freetype may be the culprit, so CCing the freetype219 as well.

I am running the latest OS X Tiger on an iBook G4, with the latest XCode installed. My versions of gimp and freetype are

freetype219-shlibs 2.2.1-4
gimp2 2.0.6-1004
gimp2-shlibs 2.0.6-1004
pango1-xft2 1.10.1-1003
pango1-xft2-shlibs 1.10.1-1003

Test case is:-

1. delete the ~/.gimp-2.0 folder and start a fresh session of gimp-2.0, taking default options
2. go to file->new and take the default options to create a new image
3. select the font tool
4. click on the new image, a character box appears
5. type a letter

Expected: letter to be echoed on screen
Actual: gimp crashes and spits out this out

======================
(gimp-2.0:2953): Pango-WARNING **: Error getting DPI from fontconfig, using 72.0
239 freetype-2.2.1/src/base/ftobjs.c: No such file or directory.
(script-fu:2956): LibGimpBase-WARNING **: script-fu: wire_read(): error
======================

I ran in verbose mode and didn't get any extra info at crash time, but here is the entire output for completeness

======================
INIT: gimp_load_config
Parsing '/sw/etc/gimp/2.0/gimprc'
Parsing '/Users/samuel/.gimp-2.0/gimprc'
Adding theme 'Default' (/sw/share/gimp/2.0/themes/Default)
Adding theme 'Small' (/sw/share/gimp/2.0/themes/Small)
Writing '/Users/samuel/.gimp-2.0/themerc'
INIT: gimp_initialize
INIT: gimp_real_initialize
INIT: gui_initialize_after_callback
INIT: gimp_restore
INIT: gui_restore_callback
INIT: gimp_real_restore
Starting extension: 'extension_script_fu'
INIT: gui_restore_after_callback
======================

I also grabbed a backtrace (attached), which seems to hint that fontconfig is the culprit, and that there is a memory access problem somewhere.

Hope this all helps to find/fix the problem. Strangely enough, the font tool is able to render/display the fonts correctly in the font choice menu, and fonts seem to work fine in other GTK+2 apps.

As an aside... I'm noting the verbose mode of gimp-2.0 spits out
"Processor instruction sets: -mmx -sse -sse2 -3dnow -altivec -vis"
but I'm pretty damn sure my PPC chip doesn't have those instruction sets! Is this a typo somewhere or is inappropriate machine code being compiled into the gimp binary?

[Sam Halliday]

[Martin Costabel]

Logged In: YES
user_id=60552
Originator: NO

Did you build gimp2 while this version of freetype219 was installed, or did you build it against an earlier version of freetype219? If the latter, then maybe rebuilding gimp2 would help.

It would also be helpful to see, in addition to the gdb backtrace, the file gimp-2.0.crash.log from your ~/Library/Logs/CrashReporter/ directory.