Package: gnucash
Version: 2.2.6-2

when launching gnucash, I get the following error:

gnucash: symbol lookup error: /usr/lib/libgnome-2.so.0: undefined
symbol: g_dgettext

Looking a bit into the problem, it seems the culprit would be
libbonobo-activation:

s...@ur:~$ ldd -r /usr/bin/gnucash-bin 
        linux-vdso.so.1 =>  (0x00007fffaf5ff000)
        libgnc-qof.so.1 => /usr/lib/gnucash/libgnc-qof.so.1 (0x00007f7ba7065000)
[...]
undefined symbol: g_set_error_literal   (/usr/lib/libgio-2.0.so.0)
undefined symbol: g_dgettext    (/usr/lib/libbonobo-activation.so.4)
undefined symbol: g_dgettext    (/usr/lib/libbonobo-2.so.0)
undefined symbol: g_dgettext    (/usr/lib/libgnome-2.so.0)
undefined symbol: g_dgettext    (/usr/lib/libgnomevfs-2.so.0)
s...@ur:~$

Running ldd on libgnome, libgnomevfs and libbonobo does not reveal 
any problem, but running it on libbonobo-activation does:

s...@ur:~$ ldd -r  /usr/lib/libbonobo-activation.so.4.0.0 
        linux-vdso.so.1 =>  (0x00007fff4c5fe000)
        libORBitCosNaming-2.so.0 => /usr/lib/libORBitCosNaming-2.so.0 
(0x00007fb544101000)
        libORBit-2.so.0 => /usr/lib/libORBit-2.so.0 (0x00007fb543e90000)
        libdl.so.2 => /lib/libdl.so.2 (0x00007fb543c8b000)
        libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00007fb543a88000)
        libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007fb543843000)
        libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00007fb54363e000)
        librt.so.1 => /lib/librt.so.1 (0x00007fb543436000)
        libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x00007fb543174000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00007fb542f58000)
        libc.so.6 => /lib/libc.so.6 (0x00007fb542c05000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fb544536000)
        libpcre.so.3 => /lib/libpcre.so.3 (0x00007fb5429d6000)
undefined symbol: g_dgettext    (/usr/lib/libbonobo-activation.so.4.0.0)

The system in question is an amd64 sid/testing machine.

Simon



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to