Inkscape crashes while opening or importing extensions .ai .eps .svg

[Roberto Delgado]

OS: Linux Mint Maya cinnamon 64
File manager: Nemo
Inkscape Version: 0.48+devel r11909

Step by step import:
1- Open Inkscape without any problem
2-Select Import from menu (also with Ctrl i)
3-Choose my document
4- Crash Message: Error message: Inkscape encountered an internal error and will close now.

This happens with any of this file extensions: .svg, .eps, .ai

Same crash occurs when opening the file by right clicking on the document>Open with Inkscape. Same while trying to open from the Main menu file>open and also with Ctrl O.

I repeat the process over 10 times and change the document names several times with different name patterns. Always the same crash result.

[dnelub (dnelub)]

I have been having same problem for a while. Inkscape crashes and gives the same error mentioned above. I was able to import .pdf and .cdr as well as .eps and .ai. However, now nothing can be imported.
At the moment I am using Inkscape 0.48+devel r11929 on Ubuntu Precise 64 bit.
I hope it is going to be solved soon.

Best wishes

[Diego (diegomestizo)]

Same problem here.

I'm using Inkscape 0.48.3.1 r9886 on Linux Mint 13 64 bits (eq. Ubuntu Precise). I'm solving the problem using sK1 and exporting to SVG, but it's hard if you're managing eps each day...

Thanks.

Diego

[su_v (suv-lp)]

> This happens with any of this file extensions: .svg, .eps, .ai

Not reproduced with Inkscape 0.48.3.1, 0.48.4 and current trunk on OS X 10.7.4
Not reproduced with Inkscape trunk r12006 on Ubuntu 12.04 (64bit, VM)
Not reproduced with Inkscape 0.48.3.1 and trunk r12006 on Ubuntu 12.10 (64bit, VM)

On all these tested systems, for example SVG and PostScript files (PS, EPS) open fine, without crash.

[su_v (suv-lp)]

Clarification:
> (…) SVG and PostScript files (PS, EPS) open fine, without crash.

Both 'File > Open' and 'File > Import' work as expected.

[Roberto Delgado (rodeloli)]

Diego (diegomestizo) I'm also doing something like that but using Karbon 14.

~suv (suv-lp) Have you tested on Linux MInt? This problem persist with files who haven't been created with Inkscape. In fact all the files are downloads. The files I were trying to open were not new ones, I had open successfully this files before at some point.

Both 'File > Open' and 'File > Import' Still not working as expected.

[Alvin Penner (apenner)]

could you attach here a file that is causing a problem?

[Roberto Delgado (rodeloli)]

Yes, here they are first ai format

[Roberto Delgado (rodeloli)]

Now one of the eps

[jazzynico (jazzynico)]

AI and EPS files from comment #7 and #8 open correctly on Windows XP, Inkscape trunk revision 12010.

[Roberto Delgado (rodeloli)]

JazzyNico (jazzynico) I already know they open correctly on windows (Vista). But thanks for checking anyway!

[su_v (suv-lp)]

AI and EPS file open correctly
- on OS X 10.7.4 (Inkscape 0.48.3.1, 0.48.4, Inkscape trunk r12010)
- Ubuntu 12.04 (Inkscape trunk r12006)
- Ubuntu 12.10 (Inkscape 0.48.3.1, Inkscape trunk r12010)

Could you please launch Inkscape from a terminal, and paste the console message here when opening or importing of the mentioned files fails?

I suspect that the issue is related to poppler, and how the package you have currently installed had been configured: maybe your distro has changed the packaging of the poppler library and no longer includes the xpdf header files which Inkscape requires to import PDF files, or possibly you have upgrade to a different poppler version from another PPA?
<http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies#Poppler>

[Roberto Delgado (rodeloli)]

Here it's the code

(inkscape:17080): Gtk-CRITICAL **: IA__gtk_widget_get_visible: assertion `GTK_IS_WIDGET (widget)' failed

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
Segmentation fault

[Roberto Delgado (rodeloli)]

Forgot to mention:

I remove version: 0.48+devel r11909

And installed version: 1:0.48+devel+12010+34~precise1

The same crash with both

[su_v (suv-lp)]

> I remove version: 0.48+devel r11909
> And installed version: 1:0.48+devel+12010+34~precise1
> The same crash with both

The problem seems less likely to be in Inkscape's codebase itself - something else on your system appears to trigger the crash, likely when it tries to open the PDF import settings dialog (EPS files are converted to PDF on-the-fly with ps2pdf, and then imported as PDF files using internal routines, and with the PDF-based AI files AFAIU the proprietary parts are stripped and the remaining content is opened as PDF).

> Here it's the code
>
> (inkscape:17080): Gtk-CRITICAL **: IA__gtk_widget_get_visible: assertion `GTK_IS_WIDGET (widget)' failed

Hmm, I'd have hoped for somewhat more verbose output :(
Any chance you could run inkscape from gdb, and create a backtrace when the crash occurs?

[Alex Valavanis (valavanisalex)]

Probably a good idea to try and trap that GTK+ warning in the backtrace:

# Run inkscape in gdb...
gdb inkscape

# Tell gdb to break when Gtk+ warning is triggered and then run Inkscape...
br g_logv
r

# Wait for breakpoint to occur, and then grab the backtrace...
bt full

[Roberto Delgado (rodeloli)]

#0 0x00007ffff0f27e00 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#1 0x00007ffff0f281b2 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x00007ffff5cb2a04 in gtk_widget_get_visible ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
No symbol table info available.
#3 0x00007ffff5b3f416 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
No symbol table info available.
#4 0x00007ffff5b4a806 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
No symbol table info available.
#5 0x00007ffff149bca2 in g_closure_invoke ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#6 0x00007ffff14acd71 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#7 0x00007ffff14b5099 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#8 0x00007ffff14b5754 in g_signal_emit_by_name ()

[Roberto Delgado (rodeloli)]

Alex Valavanis (valavanisalex)

That help?

[Alex Valavanis (valavanisalex)]

Hi rodeloli,

Thanks for that. Unfortunately, it looks like there weren't any debugging symbols available on your system. Also, the backtrace doesn't show which call from Inkscape caused the problem.

Perhaps you could confirm... do you see the same problem if you use the latest stable version of Inkscape from the official Ubuntu/Mint repositories (rather than our PPA)?

[Roberto Delgado (rodeloli)]

Alex Valavanis

> Perhaps you could confirm... do you see the same problem if you use the latest stable version of Inkscape from the official >Ubuntu/Mint repositories (rather than our PPA)?
>
I have installed the stable version from the software manager (Mint). The result is the exactly the same. :(

~suv

>I suspect that the issue is related to poppler, and how the package you have currently installed had been configured: maybe >your distro has changed the packaging of the poppler library and no longer includes the xpdf header files which Inkscape >requires to import PDF files, or possibly you have upgrade to a different poppler version from another PPA?
>
I'm also using development versions of Scribus and Gimp. I don't know if this could affect Inkscape.

The only thing that changes after downgrade was the man-db. While unistalling Inkscape-trunk via Synaptic mark man-db as not going to be removed. After installation of stable version the system makes an update or downgrade (not sure) of man-db.

[Alex Valavanis (valavanisalex)]

> I'm also using development versions of Scribus and Gimp. I don't know if this could affect Inkscape.

Possibly, if either of those come bundled with copies of libraries that Inkscape uses. However, the Inkscape package should ensure that you have the correct dependencies available... unless they've since been overwritten!

You can grab the Inkscape debug symbols that go with your package version by following the guide at https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages

After that, hopefully the gdb output should give some more specific information about what's causing the crash.

Thanks very much for helping with this.

[Roberto Delgado (rodeloli)]

Alex Valavanis (valavanisalex)

Sorry Ilm late with my response. I had to have some sleep (over 24 hrs working :)

> You can grab the Inkscape debug symbols that go with your package version by following the guide at https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages
>

I was trying to grab the Inkscape debug symbols but in update process something goes wrong. Here is the terminal msg.

W: Failed to fetch http://ddebs.ubuntu.com/dists/maya/main/binary-amd64/Packages 404 Not Found

W: Failed to fetch http://ddebs.ubuntu.com/dists/maya/restricted/binary-amd64/Packages 404 Not Found

W: Failed to fetch http://ddebs.ubuntu.com/dists/maya/universe/binary-amd64/Packages 404 Not Found

W: Failed to fetch http://ddebs.ubuntu.com/dists/maya/multiverse/binary-amd64/Packages 404 Not Found

W: Failed to fetch http://ddebs.ubuntu.com/dists/maya/main/binary-i386/Packages 404 Not Found

W: Failed to fetch http://ddebs.ubuntu.com/dists/maya/restricted/binary-i386/Packages 404 Not Found

W: Failed to fetch http://ddebs.ubuntu.com/dists/maya/universe/binary-i386/Packages 404 Not Found

W: Failed to fetch http://ddebs.ubuntu.com/dists/maya/multiverse/binary-i386/Packages 404 Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.

I also remove --purge Scribus and Gimp to remove the posibility of there was something conflicting, but no success.

You're welcome! I'm here to help Inkscape dev in all I can.

[Roberto Delgado (rodeloli)]

I have noticed something odd while crashing Inkscape from gdb, the crash never completes, only freezes and stay with the file manager open like fore ever. That's maybe why there is no debug symbols or report at all.

[Roberto Delgado (rodeloli)]

Ok, I think I know what's happening or at least how to temporarily solve it. I get rid of this issue by removing the Nemo file manager and all the Linux Mint 14 Nadia backports. I think that's what's causing the problem because Inkscape is now working as expected. All the file extensions are opening.

This problem can be fixed by removing and turning off Linux Mint backports and Romeo unstable repositories (On Mint 13 Maya).

[Roberto Delgado (rodeloli)]

>>Ok, I think I know what's happening or at least how to temporarily solve it. I get rid of this issue by removing the Nemo file manager and all the Linux Mint 14 Nadia backports. I think that's what's causing the problem because Inkscape is now working as expected. All the file extensions are opening.

This problem can be fixed by removing and turning off Linux Mint backports and Romeo unstable repositories (On Mint 13 Maya).<<

This is not the solution at all. After I istalled some new software and after an update the problem came back. Now I can open .SVG but no .AI extensions. I'm unistalling added software one by one to see if the problem is conflict with one of them. I will report the progress asap.

[dnelub (dnelub)]

As I have the same problem (#1 comment), I'd love to help more in order to solve this problem because it gives to me lot of trouble.

By the way I am getting exactly same error as it is told in #12 comment.

(inkscape:6363): Gtk-CRITICAL **: IA__gtk_widget_get_visible: assertion `GTK_IS_WIDGET (widget)' failed

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
Segmentation fault (core dumped)

[Roberto Delgado (rodeloli)]

Ok, this is definitively a conflict with Gimp or Scribus. I have switch to Ubuntu Studio and the same error occurs here after installing the software Scribus and Gimp devs. I have run inkscape from gdb.

Starting program: /usr/bin/inkscape
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdc580700 (LWP 8653)]
[New Thread 0x7fffdbd7f700 (LWP 8654)]
[New Thread 0x7fffdb57e700 (LWP 8655)]
[Thread 0x7fffdb57e700 (LWP 8655) exited]
[Thread 0x7fffdbd7f700 (LWP 8654) exited]
[New Thread 0x7fffdbd7f700 (LWP 8656)]
[New Thread 0x7fffdb57e700 (LWP 8657)]
[New Thread 0x7fffdad6c700 (LWP 8658)]
[Thread 0x7fffdb57e700 (LWP 8657) exited]
[Thread 0x7fffdad6c700 (LWP 8658) exited]
[Thread 0x7fffdc580700 (LWP 8653) exited]
[New Thread 0x7fffdc580700 (LWP 8659)]
[Thread 0x7fffdc580700 (LWP 8659) exited]
[New Thread 0x7fffdc580700 (LWP 8660)]
[New Thread 0x7fffdad6c700 (LWP 8661)]
[Thread 0x7fffdbd7f700 (LWP 8656) exited]
[Thread 0x7fffdc580700 (LWP 8660) exited]

(inkscape:8649): Gtk-CRITICAL **: IA__gtk_widget_get_visible: assertion `GTK_IS_WIDGET (widget)' failed

Program received signal SIGSEGV, Segmentation fault.
0x00007fffebbea518 in Page::createGfx(OutputDev*, double, double, int, bool, bool, int, int, int, int, bool, bool (*)(void*), void*) ()
   from /usr/lib/x86_64-linux-gnu/libpoppler.so.28
(gdb) bt full
#0 0x00007fffebbea518 in Page::createGfx(OutputDev*, double, double, int, bool, bool, int, int, int, int, bool, bool (*)(void*), void*) ()
   from /usr/lib/x86_64-linux-gnu/libpoppler.so.28
No symbol table info available.
#1 0x00007fffebbea89e in Page::displaySlice(OutputDev*, double, double, int, bool, bool, int, int, int, int, bool, bool (*)(void*), void*, bool (*)(Annot*, void*), void*) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.28
No symbol table info available.
#2 0x00007ffff170ac2a in ?? ()
   from /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
No symbol table info available.
#3 0x00000000005e6298 in ?? ()
No symbol table info available.
#4 0x00000000005e79fa in ?? ()
No symbol table info available.
#5 0x00000000005e82bb in ?? ()
No symbol table info available.
#6 0x00000000005c74da in ?? ()
No symbol table info available.
#7 0x00000000005c5205 in ?? ()
No symbol table info available.
#8 0x0000000000478536 in ?? ()
No symbol table info available.

[su_v (suv-lp)]

> Program received signal SIGSEGV, Segmentation fault.
> 0x00007fffebbea518 in Page::createGfx(OutputDev*, double, double, int, bool, bool, int, int, int, int, bool, bool (*)(void*), void*) ()
> from /usr/lib/x86_64-linux-gnu/libpoppler.so.28

See comment #11 … did you compare the poppler versions
- originally installed (inkscape packages usually are compiled and linked against this one)
- the updated one from the GIMP/Scribus development PPAs

[Roberto Delgado (rodeloli)]

In the screenshot attached you can see the different poppler libraries installed in my system. For the documentation you reffer me I can see is better if we only use one poppler version " Poppler are not ABI compatible".

But I don't know to much about this. I'm a designer, tell me what to do or how I can help on this.

Thanks for your hard work!

[su_v (suv-lp)]

> In the screenshot attached you can see the different poppler libraries
> installed in my system.

@Alex Valavanis - maybe you can shed some light on what happens here? TBH I'm not really familiar with how multiple runtime versions of poppler are managed on linux (or Ubuntu) - my own build environment setup for inkscape (on OS X) only keeps the most recent version around, and always requires to rebuild applications like inkscape, gimp and evince whenever the so-version of poppler changes (which unfortunately happens almost every time poppler is upgraded, even with minor dot releases).

[Alex Valavanis (valavanisalex)]

Hi, yes, as far as I know you should always run a rebuild whenever the so-name changes.

The pre-build binaries from the Ubuntu Precise PPA will have been compiled against Poppler 0.18.4 (so-name=19).

@rodeloli - if you've installed a newer version of Poppler on your system then I guess anything that uses Poppler should be recompiled. I suggest that you:

* Uninstall Inkscape completely
* Make sure that you have the latest Poppler headers and binaries installed
* Download the Inkscape source code package, compile it and install it yourself

[Alex Valavanis (valavanisalex)]

Just to confirm... did you compile and install the new version of Poppler from source code... or did you grab a binary package from a repository somewhere?

[Roberto Delgado (rodeloli)]

@Alex Valavanis

* I installed Inkscape from the ppa (cafuego) via terminal. I always add the repositories and install devs from terminal because it automate / suggest all dependencies.
* No, I never do anything related to the Poppler.

[Roberto Delgado (rodeloli)]

Ok, to solve this problem the better option is to upgrade the distro to Quantal "12.10". Poppler is outdated in the Precise distribution (is using version 20) and the actual stable version is 22. I have upgrade Ubutu Studio to 12.10 and now Inkscape is working as expected.

[dnelub (dnelub)]

Thx rodeloli,

After upgrading to Quantal 12.10, the problem is gone.

PS: Like rodeloli, I also use development versions of Scribus, Gimp and blender.

[Roberto Delgado (rodeloli)]

@dnelub You're very welcome,

I'm happy this works for you too. I know we can solve this by manually upgrading the poppler library but, in my experience this could maybe represent future crashes of other applications. That's why I recommend to upgrade the distro instead of only upgrade the library.

Now we are happy campers!

[ScislaC (scislac)]

Does that mean we can close this bug report?

[Roberto Delgado (rodeloli)]

I think so!

[su_v (suv-lp)]

Closing as 'Invalid' for project Inkscape: apparently an different poppler version which is not ABI-compatible to the one the distro's Inkscape package was built and linked against, was installed by custom PPA with development builds for Scribus/GIMP.

Feel free to reopen if you think this bug was closed in error.

[Dimitar (dimi-des)]

any way of fixing this issue with re-compiling inkscape? as a non-dev I have no idea how to compile packages, yet it is a critical issue to be able to work with PDFs in inkscape. And I have a feeling that upgrading to 12.10 will cause many other issues.

[Dimitar (dimi-des)]

sorry mean to sea if there is way to fix this without* recompiliing inkscape

[Dimitar (dimi-des)]

ok, followed the advice, and also upgraded to 12.10, now I can open PDFs again in Inkscape. Thanks :)

[luojie-dune (luojie-dune)]

I had the same issue after installing scribus-trunk.

The cause is poppler lib. After downgrade them to the those provided in Official repository, no crash anymore.