segfault on gimp from gtk

[Jim Sabatke <jsabatke gmail com>]

This was originally sent to the gimp list, but appears to be a gtk issue.

Message #1

Carol Spears wrote:
> On Thu, May 04, 2006 at 06:45:32PM -0500, Jim Sabatke wrote:
>> I have been updating all my machines to gimp 2.2.10.  It works fine 
on all of them except for my HP ZD 7000 laptop.  2.2.0 worked fine on 
this box.  I'm getting the infamous wire_read error whenever I try to 
open a file.  I've googled for some time and there seem to be countless 
solutions, none of which work for me.  The error I get is:
>>
>> Segmentation fault
>> jim mugsy:~/programs/media/gimp-2.2.10>
>> (script-fu:8117): LibGimpBase-WARNING **: script-fu: wire_read(): error
>>
> that is a message that is sent by a healthy script-fu server when gimp
> crashes.
>
> i wonder if your gimp is using the old gimp libraries.

I don't think so.  Here is a ldd dump:

jim mugsy:~/programs/media/gimp-2.2.10> ldd /opt/gnome/bin/gimp2
        libgimpwidgets-2.0.so.0 => 
/opt/gnome/lib/libgimpwidgets-2.0.so.0 (0x4003c000)
        libgimpmodule-2.0.so.0 => /opt/gnome/lib/libgimpmodule-2.0.so.0 
(0x40117000)
        libgimpcolor-2.0.so.0 => /opt/gnome/lib/libgimpcolor-2.0.so.0 
(0x4011c000)
        libgimpthumb-2.0.so.0 => /opt/gnome/lib/libgimpthumb-2.0.so.0 
(0x40125000)
        libgimpmath-2.0.so.0 => /opt/gnome/lib/libgimpmath-2.0.so.0 
(0x4012e000)        libgimpbase-2.0.so.0 => 
/opt/gnome/lib/libgimpbase-2.0.so.0 (0x40133000) libgtk-x11-2.0.so.0 => 
/opt/gnome/lib/libgtk-x11-2.0.so.0 (0x40140000)
        libgdk-x11-2.0.so.0 => /opt/gnome/lib/libgdk-x11-2.0.so.0 
(0x403fc000)
        libatk-1.0.so.0 => /opt/gnome/lib/libatk-1.0.so.0 (0x40475000)
        libgdk_pixbuf-2.0.so.0 => /opt/gnome/lib/libgdk_pixbuf-2.0.so.0 
(0x4048d000)
        libm.so.6 => /lib/i686/libm.so.6 (0x404a2000)
        libpangoxft-1.0.so.0 => /opt/gnome/lib/libpangoxft-1.0.so.0 
(0x404c6000)        libpangox-1.0.so.0 => 
/opt/gnome/lib/libpangox-1.0.so.0 (0x404cd000)
        libart_lgpl_2.so.2 => /opt/gnome/lib/libart_lgpl_2.so.2 
(0x404d8000)
        libpangoft2-1.0.so.0 => /opt/gnome/lib/libpangoft2-1.0.so.0 
(0x404ee000)        libpango-1.0.so.0 => 
/opt/gnome/lib/libpango-1.0.so.0 (0x40514000)
        libgobject-2.0.so.0 => /opt/gnome/lib/libgobject-2.0.so.0 
(0x4054d000)
        libgmodule-2.0.so.0 => /opt/gnome/lib/libgmodule-2.0.so.0 
(0x40584000)
        libdl.so.2 => /lib/libdl.so.2 (0x40588000)
        libglib-2.0.so.0 => /opt/gnome/lib/libglib-2.0.so.0 (0x4058b000)
        libfontconfig.so.1 => /usr/local/lib/libfontconfig.so.1 
(0x4060f000)
        libfreetype.so.6 => /usr/local/lib/libfreetype.so.6 (0x4063d000)
        libc.so.6 => /lib/i686/libc.so.6 (0x406a6000)
        libpangocairo-1.0.so.0 => /opt/gnome/lib/libpangocairo-1.0.so.0 
(0x407da000)
        libz.so.1 => /lib/libz.so.1 (0x407e2000)
        libcairo.so.2 => /opt/gnome/lib/libcairo.so.2 (0x407f1000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40830000)
        libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x4092c000)
        libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x40935000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40939000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
        libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x40947000)
        libexpat.so.0 => /opt/gnome/lib/libexpat.so.0 (0x40959000)
jim mugsy:~/programs/media/gimp-2.2.10>

>
> did you build this gimp yourself or did your distribution install it?

I built it myself, which I am accustomed to doing.  I am on SuSE 9.0 
boxes, so everything basically goes into /opt/gnome.

>
> one quick way to check to see if it is using the wrong library is to:
> jim mugsy:~> whereis gimp
>
> and
> jim mugsy:~> whereis libgimp

They are both correct.

>
> if you have some gimp stuff in /usr/lib and also in /usr/local/lib that
> would be what is making the crash.
>
> if you still have the gimp-2.2.0 sources around, as root, "make
> uninstall"  and then in the new gimp-2.2.10 sources, "make install"
> again.

I also had already done this.  I don't like stray stuff laying around.

>
> let me know how this goes
>
> carol
>
>

Thanks for you help.

Jim


***************************************************************

message #2

Here's some more info.  I ran gcc on it and here is the debug info after 
trying to open a file:

[Switching to Thread 16384 (LWP 14365)]
0x401f6595 in error_message_with_parent (parent=0x0,
    msg=0x8bfcdb8 "Could not retrieve information about the file",
    detail=0x8bfce20 "error accessing 'file:///home/jim': Invalid URI")
    at gtkfilechooserdefault.c:962
962       if (parent->group)


Jim