inkscape 0.91-3ubuntu1 on Ubuntu 15.04 crashes on startup

Bug #1458163 reported by Frank K.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
Undecided
Unassigned

Bug Description

Starting Inkscape from Start-Icon produces an Error Popup "Inkscape found an internal error and will be closed now" (In German as I'm on an German System).
Trying to start Inkscape from a Console-Window (inkscape > Inkscape_Problem.log 2>&1) produces the Errors seen in the Attached File.
Mainly: terminate called after throwing an instance of 'Glib::FileError'

I am using the pakage provided by Ubuntu repository.
But have same problerm when using pakage provided on Inkscape home page.

I have the same Problem when I use the pakage from Inkscape-Site via PPA.

I uninstalled and reinstalled Inkscape several times. But this didn't help.

Tags: crash linux
Revision history for this message
Frank K. (frank64) wrote :
Revision history for this message
Frank K. (frank64) wrote :

Forgot to mention: 64 bit System

Revision history for this message
su_v (suv-lp) wrote :

Based on information provided by one of the core devs, this is a local problem on your system with wrong linkage. Could you please check whether you have custom versions of gtk2 and/or glib installed?

$ apt-cache policy libgtk2.0-0
$ apt-cache policy libglib2.0-0

--
Replaces hidden comment #2 to fix typo in Gtk+ version (s/Gtk1/gtk2)

Changed in inkscape:
status: New → Incomplete
tags: added: linux
removed: 0.91 15.04 inkscape on ubuntu
Revision history for this message
Frank K. (frank64) wrote :

frank@frank-ubuntu-5:~$ apt-cache policy libgtk2.0-0
libgtk2.0-0:
  Installiert: 2.24.27-0ubuntu1
  Installationskandidat: 2.24.27-0ubuntu1
  Versionstabelle:
 *** 2.24.27-0ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
        100 /var/lib/dpkg/status
frank@frank-ubuntu-5:~$

frank@frank-ubuntu-5:~$ apt-cache policy libglib2.0-0
libglib2.0-0:
  Installiert: 2.44.0-1ubuntu3
  Installationskandidat: 2.44.0-1ubuntu3
  Versionstabelle:
 *** 2.44.0-1ubuntu3 0
        500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
        100 /var/lib/dpkg/status
frank@frank-ubuntu-5:~$

Revision history for this message
Frank K. (frank64) wrote :
su_v (suv-lp)
Changed in inkscape:
status: Incomplete → New
Revision history for this message
jazzynico (jazzynico) wrote :

Not reproduced on Xubuntu 15.04 (64bit), same gtk and glib versions as in comment #5.
Tested with Inkscape 0.91-3ubuntu1 and trunk rev. 14205 (compiled locally).

Revision history for this message
Frank K. (frank64) wrote :

Hi all,

has there been any new ideas regarding my problem ?
I'm missing my Inkscape...

Greetings
-Frank-

Revision history for this message
jazzynico (jazzynico) wrote :

Hi Frank,

Did you upgrade to Ubuntu 15.10? If so, are you still affected by the same bug when launching the updated Inkscape package?

Your log file seems to be related to Bug #898704 "MacPort Inkscape on Lion crash at startup"<https://bugs.launchpad.net/inkscape/+bug/898704>. At least, you share the same startup message.

I also ran into the same messages a long time ago when playing with several different Inkscape builds (I don't remember if it was between versions -0.48.x and 0.91- or between gtk2 and gtk3 builds). If I remember correctly, I fixed it by uninstalling everything (including the whole /usr/share/inkscape folder) and then reinstalling. But since I usually play with locally compiled Inkscape builds, the context is a bit different.

Revision history for this message
Frank K. (frank64) wrote :

Hi jazzynico,

yes, I upgraded to Ubuntu 15.10 and the Problem went away.

More detailed:
I Installed 15.10 on a new disk. So I had a clean drive/system after the install.
So no old gtk and files to deal with...
That was maybe the trick.

Now everything works fine on 15.10

Revision history for this message
jazzynico (jazzynico) wrote :

Happy to see it's fixed for you! Thanks for reporting back, Frank!

Changed in inkscape:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.