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 128948 - crash on startup .. load fonts
crash on startup .. load fonts
Status: RESOLVED DUPLICATE of bug 121752
Product: GIMP
Classification: Other
Component: General
1.x
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2003-12-10 04:05 UTC by Thomas Drillich
Modified: 2003-12-11 12:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Thomas Drillich 2003-12-10 04:05:01 UTC
gimp crashes at loading fonts, maybe it's a fontconfig error ? 
 
---- start of console output ---- 
>gimp-1.3 --verbose -c 
This is a development version of The GIMP. 
Debug messages may appear here. 
 
INIT: gimp_load_config 
»/etc/gimp/1.3/gimprc« wird verarbeitet 
»/home/drillich/.gimp-1.3/gimprc« wird verarbeitet 
gimp_composite: use=yes, verbose=no +mmx +sse -sse2 -3dnow -altivec -vis 
Thema »Small« wird hinzugefügt (/usr/share/gimp/1.3/themes/Small) 
Thema »Default« wird hinzugefügt (/usr/share/gimp/1.3/themes/Default) 
»/home/drillich/.gimp-1.3/themerc« wird geschrieben 
Fontconfig warning: line 248: invalid edit binding "same" 
Fontconfig warning: line 260: invalid edit binding "same" 
INIT: gimp_initialize 
INIT: gimp_real_initialize 
INIT: gui_initialize_after_callback 
INIT: gimp_restore 
Fontconfig warning: line 248: invalid edit binding "same" 
Fontconfig warning: line 260: invalid edit binding "same" 
gimp-1.3: fatal error: Speicherzugriffsfehler 
-------------- end of console output ----------------------
Comment 1 Michael Natterer 2003-12-10 11:27:53 UTC
We need some more info to debug this.
Would you try running gimp as follows:

> gdb gimp-1.3
(gdb) run

and when it segfaults enter:

(gdb) bt

at the gdb prompt and add the stack trace as comment to
this bug?
Comment 2 Sven Neumann 2003-12-10 12:40:38 UTC
This looks common; most probably the well-known fontconfig bug that
has been reported a few times. In order to verify that fonts are
indeed the problem, you can start gimp-1.3 with the --no-fonts
command-line option.
Comment 3 Thomas Drillich 2003-12-10 19:35:48 UTC
 
stack trace: 
gdb gimp-1.3 results: 
---- 
Program received signal SIGSEGV, Segmentation fault. 
0x40568a74 in FcEditDestroy () from /usr/X11R6/lib/
libfontconfig.so.1 
(gdb) bt 
  • #0 FcEditDestroy
    from /usr/X11R6/lib/
  • #1 FcSubstDestroy
    from /usr/X11R6/lib/
  • #2 FcConfigDestroy
    from /usr/X11R6/lib/
  • #3 FcConfigSetCurrent
    from /usr/X11R6/lib/
  • #4 gimp_fonts_load
  • #5 gimp_restore
  • #6 app_run
  • #7 main
 
 
Running 'gimp-1.3 --no-fonts' starts complete without any problems, 
exept there are no fonts in app ;-) 
 
I saw some apps (eg. quanta), which produces the same warning,  
but do not crash ? 
 
Comment 4 Sven Neumann 2003-12-11 12:58:25 UTC
Updating to fontconfig-2.2 should fix your problem.

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