Inkscape crahes when textext (LateX extension) element is added

Bug #1230362 reported by Lothar Birk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
Undecided
Unassigned

Bug Description

Hi,

I have a small inkscape sketch (attched) which crashes when I add a
TeX Extenstion (textext.py version 0.44) element.

I run a Linux Mint 13 (64bit) system with inkscape 0.48.3.1 r9886 (Jan 29 2013).

The backtrace for the crash is:
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/bin/inkscape...(no debugging symbols found)...done.
(gdb) run
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 0x7fffdf786700 (LWP 23872)]

Program received signal SIGSEGV, Segmentation fault.
0x00000000007cf157 in Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension::Effect*, Inkscape::UI::View::View*, Inkscape::Extension::Implementation::ImplementationDocumentCache*) ()
(gdb) bt
#0 0x00000000007cf157 in Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension::Effect*, Inkscape::UI::View::View*, Inkscape::Extension::Implementation::ImplementationDocumentCache*) ()
#1 0x0000000000b55c3d in Inkscape::Extension::ExecutionEnv::run() ()
#2 0x00000000007ca06c in Inkscape::Extension::Effect::effect(Inkscape::UI::View::View*) ()
#3 0x00000000007ca1b5 in Inkscape::Extension::Effect::prefs(Inkscape::UI::View::View*) ()
#4 0x000000000080e302 in sp_action_perform(SPAction*, void*) ()
#5 0x00007ffff4732ca2 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6 0x00007ffff4743d71 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7 0x00007ffff474c099 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8 0x00007ffff474c242 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9 0x00007ffff5ea338e in gtk_widget_activate () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#10 0x00007ffff5d9e0fd in gtk_menu_shell_activate_item () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#11 0x00007ffff5d9e495 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#12 0x00007ffff5d89dd8 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#13 0x00007ffff4732ca2 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x00007ffff4744339 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x00007ffff474bd7e in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x00007ffff474c242 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x00007ffff5ea4191 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#18 0x00007ffff5d87f63 in gtk_propagate_event () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#19 0x00007ffff5d882c3 in gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#20 0x00007ffff59fccac in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#21 0x00007ffff4475d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007ffff44760a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007ffff447649a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007ffff5d872f7 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#25 0x000000000065e010 in sp_main_gui(int, char const**) ()
#26 0x0000000000643468 in main ()

Thanks for looking into this.

Revision history for this message
Lothar Birk (birk-z) wrote :
Revision history for this message
su_v (suv-lp) wrote :

Based on the Inkscape version
> inkscape 0.48.3.1 r9886 (Jan 29 2013)
and the id of <sodipodi:namedview> of the provided sample SVG file:
> id="namedview6173"

this is a duplicate report of a known regression in Inkscape 0.48.3.1 (fixed in 0.48.4):
- Bug #944077 “inkscape crashed with SIGSEGV in Inkscape::Extension::Implementation::Script::effect()”
  <https://bugs.launchpad.net/inkscape/+bug/944077>

Workaround for affected files:
<https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/944077/comments/11>

Note that the same trigger (id string for <namedview> element) is e.g. present when opening PDF/PS/EPS files in Inkscape for editing, as described in
<https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/944077/comments/10>

Please add a comment here and revert the duplicate status if you don't agree and think these are different issues.

tags: added: crash extensions-plugins
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.