GNOME Bugzilla – Bug 121814
Gimp crashes at startup
Last modified: 2003-09-10 08:34:39 UTC
I have had no such problem with previous devel versions of gimp. The 1.3.19 was starting fine 2 days ago, but 1.3.20 refuses to start, just displays the splash screen and crashes (segmentation fault). From the command line, I could take this (between dashes): ---------------------------------- [olive@localhost olive]$ gimp-1.3 This is a development version of the GIMP Debug messages may appear here. Testing CPU features... mmx : yes 3dnow : yes mmxext : yes sse : no sse2 : no gimp_composite: use=yes, verbose=no +mmx +sse +3dnow gimp-1.3: fatal error: Segmentation fault gimp-1.3 (pid:4707): [E]xit, [H]alt, show [S]tack trace or [P]roceed: s
+ Trace 40053
The options of my configure are: --prefix=/usr --disable-print --enable-python --enable-gtk-doc As I use a Mandrake 9.1 so the glib and gtk are 2.2.1, gcc is 3.2.2, kernel 2.4.20 and XFree 4.3.0, but previous version (1.3.19) was issuing a warning about gtk and not crashing. The processor is an Athlon.
This looks like another duplicate of bug #121752. This seems to affect several Linux distributions. I am curious: is there any current Linux distribution that provides the correct set of packages so that the GIMP does not crash on startup? So far, problems have been reported with the latest version of SuSE and the latest version of Mandrake. Is it working out of the box with RedHat, or do we have to expect more bug reports? *** This bug has been marked as a duplicate of 121752 ***
1- sorry for the duplicate, but I had not found any via the page http://bugzilla.gnome.org/buglist.cgi?product=GIMP&changedin=7 (I do not see font related issue in my stack trace) 2- there are redhat 9 rpms available here http://www.gnome.org/~drc/gimp-rpms/ so I guess RH9 has no problem (but it is only a guess).
Hi Olivier! You wrote: "I do not see font related issue in my stack trace". But the crash happens in gimp_fonts_init(), so this is most probably related to the fonts. However, your stack trace is indeed a bit different from the ones shown in bug #121752 and bug #121780. So maybe this is not a real duplicate. Could you test if upgrading fontconfig solves your problem? If the GIMP is still crashing after upgrading fontconfig, then we would have to re-open this bug.
What I meant was it crashed at startup, not while changing fonts. That's why I was misleaded by the "segfault while loading fonts" and thought it was not related. I'll try this if I can find a src rpm or a mandrake rpm of fontconfig somewhere (in other words, does someone has a link, I'll be thankful, because all I have at present is cooker src.rpm for 2.2.1 and I don't trust it a lot). It might take a few days (dependancies?), and I will report here the results.
Here is the answer: Yes fontconfig 2.2.1 solved the problem. Does this mean than when Gimp 1.4, oups sorry 2.0 ;) will be out, there will be no distribution that will support it? (apart maybe from the mdk 9.2 and similar extremely newest versions)
Thanks for confirming that the issue came from fontconfig. Yes, you are right: gimp-2.0 will probably no build out-of-the-box on most systems (Linux or others). Most people will have to upgrade one or several packages on their machine. The packages that are the most likely to require an upgrade are fontconfig (2.2 or later), pango (with support for freetype2) and gtk+ (2.2.2 or later). Note that the configure script has recently been modified by Mitch: it will now stop the build if you do not have the required version of fontconfig. This will help catching the problem earlier, instead of crashing the application after it was built.