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 131309 - Segmentation fault at startup
Segmentation fault at startup
Status: RESOLVED DUPLICATE of bug 121752
Product: GIMP
Classification: Other
Component: General
1.x
Other Linux
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2004-01-13 04:24 UTC by davidburge
Modified: 2004-01-13 10:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description davidburge 2004-01-13 04:24:24 UTC 
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 248: invalid edit binding "same"
Fontconfig warning: line 260: invalid edit binding "same"
Fontconfig warning: line 248: invalid edit binding "same"
Fontconfig warning: line 260: invalid edit binding "same"
gimp: fatal error: Segmentation fault
gimp (pid:2853): [E]xit, [H]alt, show [S]tack trace or [P]roceed: S

+ Trace 43179

  • #0 g_on_error_stack_trace
    from /usr/lib/libglib-2.0.so.0
  • #1 _IO_file_jumps
    from /lib/tls/libc.so.6
  • #2 ??
  • #3 ??
  • #4 ??
    from /usr/lib/libglib-2.0.so.0
  • #5 ??
  • #6 ?? 






Comment 1


Sven Neumann





          2004-01-13 10:21:41 UTC
        



This is almost certainly the well-known problem with fontconfig.
Please update to a newer version of font-config.

Removing the STACKTRACE keyword since the stack-trace is unusable
because of lack of debugging symbols.

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