GNOME Bugzilla – Bug 139552
segment fault while loading fonts libfontconfig
Last modified: 2004-04-10 11:31:39 UTC
start the application in debian unstable. Here is the output from gdb: 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" Program received signal SIGSEGV, Segmentation fault. 0x40573a74 in FcEditDestroy () from /usr/X11R6/lib/libfontconfig.so.1 (gdb) backtrace
+ Trace 45867
That's a fontconfig bug which, I think, is fixed in newer releases. What version of fontconfig are you using?
The backtrace points to /usr/X11R6/lib/libfontconfig.so.1 which is probably fontconfig-1.0.2; please ensure that *only* fontconfig >= 2.2.0 is in your system (usually located in /usr/lib/libfontconfig.so.1). Find some tips in bug #135878. *** This bug has been marked as a duplicate of 121752 ***
I don't believe this is a duplicate of 121752, because I have font config version 2.2.2-2 installed. The latest version available on debian unstable. Bug #121752 was resolved by upgrading to font config version 2.2. The stack trace looks a little bit different too.
The questions are (a) are you sure that fontconfig-2.2 is being used here? There might be a different version on your system which is used instead. You can use ldd to figure this out. (b) did you regenerate the font cache files after the update?
The debian gimp package maintainer removed our runtime check for fontconfig, for reasons unknown. To reiterate what Pedro said, Debian installs fontconfig in /usr/lib, so the library in /usr/X11R6/lib is very likely an older version. You should not have more than one copy of a library in system paths, so you need to fix your system. Ari, can you *please* add the runtime check back for the debian package. It is a very simple way to identify broken setups.
See also bug #137814 where this runtime check catched the very same problem again on Debian. Perhaps a solution is to make the message more verbose, something in the line of: "An old version of Fontconfig (x.y.z) is being loaded instead of the required one which is 2.2.0 or better. This may be caused by a second libfontconfig.so.1 being installed in the system, probably in /usr/X11R6/lib - please correct the situation or report it to someone who can." I don't have an installation where this problem is shown but perhaps a workaround is to run gimp with LD_LIBRARY_PATH set to /usr/lib?
Manish, The problem has been fixed. I deleted the libfontconfig libraries in /usr/X11R6/lib as you insinuated I should. Thanks! Daniel p.s. I did the "ldd" thing but I couldn't extract clues from the output initially. Now I can.
I think we should change the message as Pedro suggested (and Ari should please reenable it for debian). Pedro, can you do change the message as suggested? The code is in app/sanity.c. The string is not marked for translation, so there's no problem changing it.
I told you I already put it back in, but the ftpmasters are being really freakin slow actually including the updated packages.
I've committed a modified text which will soon appear in release 2.0.1: 2004-04-10 Pedro Gimeno * app/core/gimpdrawable-transform.c (gimp_drawable_transform_tiles_affine): Applied patch from William Skaggs that addresses bug #120490. * app/sanity.c (sanity_check): Modified the message that reports an old version of Fontconfig in an attempt to make it more informative.