Julien BLACHE wrote:
Eric Van Buggenhaut <e...@proyectosolidario.org> wrote:

Hi,

(xsane:4731): GdkPixbuf-WARNING **: Error loading XPM image loader:
Unable to load image-loading module:
/usr/lib32/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so:
/usr/lib32/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so: cannot open
shared object file: No such file or directory

(xsane:4731): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xf71d68c0 (LWP 4731)]
0xf7826bc0 in IA__g_object_ref (_object=0xf7c70ada) at
/build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gobject.c:1718
1718
/build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gobject.c:
No such file or directory.
        in
/build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/gobject/gobject.c

OK, this is definitely not an XSane issue.

I still don't know why GTK goes looking for its loaders under
/usr/lib32, which it would only do if you were running i386 binaries
on an otherwise amd64 system. I don't think you're doing that here, or
are you?

Looks like a broken system to me.


AFAIK, there's nothing in that system that comes from amd64. I could try reinstalling some package and see if that fixes the problem. Which gtk package is exactly involved?

Thanks
--
Eric




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to