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

Hi,

This is a amd64 kernel with a i386 debian system installed.

no ia32 package:

e...@toledo1:~$ dpkg -l|grep ia32
e...@toledo1:~$

Just tell me any command you'd like me to execute.

Did you upgrade this machine from a previous Debian release? If yes,
can you try to remove ~/.sane/xsane and try again? XSane's config
files are not necessarily compatible from one version to the
other.

Removing .sane didn't help:

r...@toledo1:~$ rm -rf .sane/
e...@toledo1:~$ xsane

(xsane:9268): 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:9268): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

(xsane:9268): 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:9268): Gdk-CRITICAL **: gdk_drawable_unref: assertion `GDK_IS_DRAWABLE (drawable)' failed

(xsane:9268): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(xsane:9268): 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:9268): 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
Segmentation fault



The fact that GTK goes looking for its modules under /usr/lib32 looks
suspicious to me, but eventually that could be the nominal behaviour.

I'd like the output of ldd /usr/bin/xsane,

e...@toledo1:~$ ldd /usr/bin/xsane
        linux-gate.so.1 =>  (0xf7f29000)
        libsane.so.1 => /usr/lib/libsane.so.1 (0xf7f0c000)
        libgimpui-2.0.so.0 => /usr/lib/libgimpui-2.0.so.0 (0xf7eef000)
libgimpwidgets-2.0.so.0 => /usr/lib/libgimpwidgets-2.0.so.0 (0xf7de0000) libgimpmodule-2.0.so.0 => /usr/lib/libgimpmodule-2.0.so.0 (0xf7ddc000)
        libgimp-2.0.so.0 => /usr/lib/libgimp-2.0.so.0 (0xf7dab000)
        libgimpmath-2.0.so.0 => /usr/lib/libgimpmath-2.0.so.0 (0xf7da6000)
libgimpconfig-2.0.so.0 => /usr/lib/libgimpconfig-2.0.so.0 (0xf7d98000) libgimpcolor-2.0.so.0 => /usr/lib/libgimpcolor-2.0.so.0 (0xf7d8c000)
        libgimpbase-2.0.so.0 => /usr/lib/libgimpbase-2.0.so.0 (0xf7d79000)
        libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xf79ee000)
        libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xf7968000)
        libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xf794d000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xf7934000)
        libm.so.6 => /lib/i686/cmov/libm.so.6 (0xf790e000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xf7904000)
        libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xf78c4000)
        libcairo.so.2 => /usr/lib/libcairo.so.2 (0xf7858000)
        libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xf781c000)
        libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xf7817000)
        libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xf7813000)
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xf775e000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0xf773a000)
        liblcms.so.1 => /usr/lib/liblcms.so.1 (0xf7706000)
        libtiff.so.4 => /usr/lib/libtiff.so.4 (0xf76b1000)
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xf7691000)
        libz.so.1 => /usr/lib/libz.so.1 (0xf767c000)
        libc.so.6 => /lib/i686/cmov/libc.so.6 (0xf7521000)
        libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xf751c000)
        librt.so.1 => /lib/i686/cmov/librt.so.1 (0xf7513000)
        libpthread.so.0 => /lib/i686/cmov/libpthread.so.0 (0xf74fa000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0xf740a000)
        libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0xf7407000)
        libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0xf7404000)
        libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xf73ff000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xf73d3000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0xf73c5000)
        libXrender.so.1 => /usr/lib/libXrender.so.1 (0xf73bc000)
        libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xf73b9000)
        libXi.so.6 => /usr/lib/libXi.so.6 (0xf73b1000)
        libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xf73ab000)
        libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xf73a1000)
        /lib/ld-linux.so.2 (0xf7f2a000)
        libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xf737a000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xf7305000)
        libdirectfb-1.0.so.0 => /usr/lib/libdirectfb-1.0.so.0 (0xf729e000)
        libfusion-1.0.so.0 => /usr/lib/libfusion-1.0.so.0 (0xf7296000)
        libdirect-1.0.so.0 => /usr/lib/libdirect-1.0.so.0 (0xf7281000)
libxcb-render-util.so.0 => /usr/lib/libxcb-render-util.so.0 (0xf727d000)
        libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0xf7276000)
        libxcb.so.1 => /usr/lib/libxcb.so.1 (0xf725e000)
        libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0xf7235000)
        libpcre.so.3 => /usr/lib/libpcre.so.3 (0xf720b000)
        libxcb-xlib.so.0 => /usr/lib/libxcb-xlib.so.0 (0xf7209000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0xf71e3000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0xf71e0000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xf71da000)
e...@toledo1:~$


and if you could obtain a
backtrace by running gdb xsane, then typing bt once xsane has crashed,
that'd help pinpoint the issue.

xsane has no debugging symbols, so i don't know how to hand you that.



--
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