GNOME Bugzilla – Bug 134369
GIMP crashes when starting font management
Last modified: 2004-03-26 11:31:58 UTC
This could be a problem of fontconfig, I dunno. What happens is: ~/.wine$ gimp This is a development version of The GIMP. Debug messages may appear here. gimp_composite: use=yes, verbose=no +mmx +sse -sse2 -3dnow -altivec -vis Fontconfig warning: line 238: invalid edit binding "same" Fontconfig warning: line 249: invalid edit binding "same" Fontconfig warning: line 238: invalid edit binding "same" Fontconfig warning: line 249: invalid edit binding "same" gimp: fatal error: Segmentation fault gimp (pid:6582): [E]xit, [H]alt, show [S]tack trace or [P]roceed: s
+ Trace 44171
If I run it through GDB, it outputs: Starting program: /usr/bin/gimp (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...This is a development version of The GIMP. Debug messages may appear here. gimp_composite: use=yes, verbose=no +mmx +sse -sse2 -3dnow -altivec -vis Fontconfig warning: line 238: invalid edit binding "same" Fontconfig warning: line 249: invalid edit binding "same" Fontconfig warning: line 238: invalid edit binding "same" Fontconfig warning: line 249: invalid edit binding "same" Program received signal SIGSEGV, Segmentation fault. 0x4056ba74 in FcEditDestroy () from /usr/X11R6/lib/libfontconfig.so.1 It could sure be a Debian-specific (linkling) problem, but I wanted to report it anyways
Please upgrade to fontconfig 2.2.0 or better. *** This bug has been marked as a duplicate of 132366 ***
The correct bug # of which this is a duplicate is 121752. Sorry for the spam. *** This bug has been marked as a duplicate of 121752 ***