Inkscape

Symbol lookup error when trying to start inkscape - help for debugging needed

Asked by Daniel Savi

Dear Inkscape devs

I'm running into a crash whenever I'm trying to start my inkscape.
Here's my command line output:
X@Y:~$ inkscape
inkscape: symbol lookup error: inkscape: undefined symbol: _ZN4Glib7ustring5eraseENS_16ustring_IteratorIN9__gnu_cxx17__normal_iteratorIPcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEEEE

My Inksacep version as reported by apt-cache:
X@Y:~$ apt-cache policy inkscape
inkscape:
  Installiert: 0.91-5ubuntu2
  Installationskandidat: 0.91-5ubuntu2
  Versionstabelle:
 *** 0.91-5ubuntu2 0
        500 http://ch.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
        100 /var/lib/dpkg/status

I'm running Kubuntu 15.10. lsb_release -a gives:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.10
Release: 15.10
Codename: wily

Apt-get doesn't report any broken dependencies. Purging inkscape and reinstalling didn't help. I've probably messed up one of the libraries Inkscape depends on. I wanted to find out which library inkscape is trying to load when it crashes, but I don't know how to set up a proper break point in gdb. Any advise how to investigate this problem would be highly appreciated.

Question information

Language:
English Edit question
Status:
Solved
For:
Inkscape Edit question
Assignee:
No assignee Edit question
Solved by:
Daniel Savi
Solved:
Last query:
Last reply:
Revision history for this message
Mc (mc...) said : 		#1

from the name of the symbol, I'd guess libglib* or libglibmm-*

Revision history for this message
Mc (mc...) said : 		#2

You can try "ldd /usr/bin/inkscape" to check that all libs seems correct; and/or sudo ldconfig to update some information if needed

Revision history for this message
Daniel Savi (gaess) said : 		#3

Thank you mc for your answer. The problem was the libglibmm-2.4.so.1 linking to a version in /usr/local/lib. I've compiled a newer version during compilation of ardour3 and added my /usr/local/lib to the linker path's. Then I forgot about it... This was breaking inkscape. Inkscape now works again when using the stock library, but ardour 3 doesn't. But that's another problem for another day. I may have to write a little start script for ardour, adding /usr/local/lib to the PATH.