Bug 135878 – seg fault in src version

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 135878 - seg fault in src version


Summary:	seg fault in src version


Status:	RESOLVED DUPLICATE of bug 121752

Product:	GIMP
Classification:	Other
Component:	General
Version:	1.x
Hardware:	Other Linux

Importance:	Normal major
Target Milestone:	---
Assigned To:	GIMP Bugs
QA Contact:	GIMP Bugs

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-03-01 21:13 UTC by Rob Hudson
Modified:	2004-03-02 17:13 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Rob Hudson 2004-03-01 21:13:16 UTC

I compiled the last GIMP.  After it completed and was installed, while
launching I got a segfault...

Here's the stack trace:

# gimp-1.3 
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-1.3: fatal error: Segmentation fault
gimp-1.3 (pid:12232): [E]xit, [H]alt, show [S]tack trace or [P]roceed: S

+ Trace 44697

#0 g_on_error_stack_trace
from /usr/lib/libglib-2.0.so.0
#1 _IO_getline
from /lib/tls/libc.so.6
#2 g_on_error_query
from /usr/lib/libglib-2.0.so.0
#3 gimp_eek
#4 gimp_fatal_error
#5 gimp_sigfatal_handler
at main.c line 602
#6 <signal handler called>
#7 FcEditDestroy
at fcxml.c line 277
#8 FcSubstDestroy
at fccfg.c line 137
#9 FcConfigDestroy
at fccfg.c line 156
#10 FcConfigSetCurrent
at fccfg.c line 225
#11 gimp_fonts_load
at gimp-fonts.c line 105
#12 gimp_restore
#13 app_run
#14 main
at main.c line 470

Comment 1 Raphaël Quinet 2004-03-02 08:40:25 UTC

You are probably using an old version of fontconfig.  You should use
version 2.2.0 or later.  Please try to following command to check the
version that you are currently running:
  pkg-config --modversion fontconfig

Anyway, thanks for the bug report but this is a duplicate of bug
#121752.  You could have easily found this by searching for
"FcSubstDestroy" or other functions shown in the stack trace up to the
one producing the crash.


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

Comment 2 Rob Hudson 2004-03-02 17:03:34 UTC

# pkg-config --modversion fontconfig
2.2.1

# pkg-config --modversion pango     
1.2.5

# pkg-config --modversion freetype2
9.5.3

Comment 3 Sven Neumann 2004-03-02 17:08:07 UTC

Well, the question is what version of fontconfig you are actually
using at runtime. You might have compiled gimp using headers from the
correct version. But this doesn't assure that the linker uses the same
version. Almost certainly it is using an outdated version from
/usr/X11R6/lib.

Comment 4 Rob Hudson 2004-03-02 17:13:57 UTC

Man you guys are good...  Once I removed an old fontconfig1.0 lib file
from /usr/X11R6/lib and also the .pc file from the pkgconfig
directory, the launched fine.  Thanks!