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 121752 - Segmentation Fault on startup while loading fonts
Segmentation Fault on startup while loading fonts
Status: RESOLVED NOTGNOME
Product: GIMP
Classification: Other
Component: General
1.x
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
: 121731 121780 121814 121837 124167 127764 128948 131309 134369 135878 137814 139552 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-09-08 10:40 UTC by James Ogley
Modified: 2004-04-09 15:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description James Ogley 2003-09-08 10:40:05 UTC
When I start GIMP 1.3.20, it seg faults, the stack trace is included below...

Testing CPU features...
  mmx     : yes
  3dnow   : no
  mmxext  : yes
  sse     : yes
  sse2    : no
 
gimp_composite: use=yes, verbose=no +mmx +sse
gimp: fatal error: Segmentation fault
gimp (pid:22136): [E]xit, [H]alt, show [S]tack trace or [P]roceed: S
  • #0 g_on_error_stack_trace
    from /usr/lib/libglib-2.0.so.0
  • #1 ??
  • #2 g_on_error_query
    from /usr/lib/libglib-2.0.so.0
  • #3 gimp_eek
  • #4 gimp_fatal_error
  • #5 <signal handler called>
  • #6 FcTestDestroy
    from /usr/X11R6/lib/libfontconfig.so.1
  • #7 FcSubstDestroy
    from /usr/X11R6/lib/libfontconfig.so.1
  • #8 FcConfigDestroy
    from /usr/X11R6/lib/libfontconfig.so.1
  • #9 FcConfigSetCurrent
    from /usr/X11R6/lib/libfontconfig.so.1
  • #10 gimp_fonts_load
  • #11 gimp_fonts_init
  • #12 gimp_restore
  • #13 app_init
  • #14 main
  • #15 __libc_start_main
    from /lib/libc.so.6

Comment 1 Sven Neumann 2003-09-08 10:57:40 UTC
Might be a duplicate of bug #121731 but the stack-trace looks different.
We will need more information like what versions of Pango, fontconfig
and  freetype2 are involved here.
Comment 2 James Ogley 2003-09-08 11:57:01 UTC
pango 1.2.5
fontconfig appears to be 1.0.2
freetype2 2.1.3
Comment 3 James Ogley 2003-09-08 11:59:42 UTC
fontconfig should be 2.0.2 I think, but it's called 1.0.2 internally
by the looks of /usr/X11R6/include/fontconfig/fontconfig.h
Comment 4 Sven Neumann 2003-09-08 12:08:31 UTC
fontconfig-2.0 is outdated and unmaintained. Please upgrade to
fontconfig-2.2 and let us know if this solves your problem.
Comment 5 James Ogley 2003-09-08 12:32:34 UTC
Yes, it did, closing...
Comment 6 Sven Neumann 2003-09-08 12:37:23 UTC
Reopening and closing with a proper resolution...
Comment 7 Raphaël Quinet 2003-09-08 23:00:29 UTC
*** Bug 121780 has been marked as a duplicate of this bug. ***
Comment 8 Raphaël Quinet 2003-09-09 07:52:10 UTC
*** Bug 121814 has been marked as a duplicate of this bug. ***
Comment 9 Sven Neumann 2003-09-09 13:42:31 UTC
*** Bug 121837 has been marked as a duplicate of this bug. ***
Comment 10 Raphaël Quinet 2003-09-09 14:08:57 UTC
Changing the subject to make it easier to find.
Comment 11 Sven Neumann 2003-09-09 14:43:46 UTC
*** Bug 121731 has been marked as a duplicate of this bug. ***
Comment 12 Dave Neary 2003-10-11 18:17:43 UTC
*** Bug 124167 has been marked as a duplicate of this bug. ***
Comment 13 Sven Neumann 2003-11-23 21:05:53 UTC
*** Bug 127764 has been marked as a duplicate of this bug. ***
Comment 14 Sven Neumann 2003-12-11 12:58:24 UTC
*** Bug 128948 has been marked as a duplicate of this bug. ***
Comment 15 Sven Neumann 2004-01-13 10:21:40 UTC
*** Bug 131309 has been marked as a duplicate of this bug. ***
Comment 16 Raphaël Quinet 2004-03-02 08:40:24 UTC
*** Bug 135878 has been marked as a duplicate of this bug. ***
Comment 17 Pedro Gimeno 2004-03-21 00:23:03 UTC
*** Bug 137814 has been marked as a duplicate of this bug. ***
Comment 18 Pedro Gimeno 2004-03-26 11:31:59 UTC
*** Bug 134369 has been marked as a duplicate of this bug. ***
Comment 19 Pedro Gimeno 2004-04-09 15:39:53 UTC
*** Bug 139552 has been marked as a duplicate of this bug. ***