Crash on flatten bezier on a particular svg.

[Franck Bettinger]

If I run inkscape 0.48 on ubuntu, load the attached svg image, click on Extensions>Modify Path>Flatten Beziers..., I get the flatten bezier dialog box. In that box, If I check the Live preview checkbox or click on apply, Inkscape crahes.

[Franck Bettinger (fbettinger)]

btw, here is the trace for that bug :

Starting program: /usr/bin/inkscape
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb5229b40 (LWP 27687)]
[New Thread 0xb48d0b40 (LWP 27688)]
[New Thread 0xa5716b40 (LWP 27692)]
[New Thread 0xa4dffb40 (LWP 27693)]
[New Thread 0xa43ffb40 (LWP 27694)]
[Thread 0xa4dffb40 (LWP 27693) exited]
[Thread 0xb48d0b40 (LWP 27688) exited]
[Thread 0xa5716b40 (LWP 27692) exited]

Program received signal SIGSEGV, Segmentation fault.
0x08401e6e in Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension::Effect*, Inkscape::UI::View::View*, Inkscape::Extension::Implementation::ImplementationDocumentCache*) ()
(gdb) bt
#0 0x08401e6e in Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension::Effect*, Inkscape::UI::View::View*, Inkscape::Extension::Implementation::ImplementationDocumentCache*) ()
#1 0x08767933 in Inkscape::Extension::ExecutionEnv::run() ()
#2 0x083f4df9 in Inkscape::Extension::ParamBoolCheckButton::on_toggle() ()
#3 0xb7b92433 in Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*) () from /usr/lib/i386-linux-gnu/libglibmm-2.4.so.1
#4 0xb71af58f in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#5 0xb71ad826 in g_closure_invoke ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#6 0xb71bf842 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#7 0xb71c7732 in g_signal_emit_valist ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#8 0xb71c78b3 in g_signal_emit ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#9 0xb7736d3a in gtk_toggle_button_toggled ()
   from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
#10 0xb7736d80 in ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
#11 0xb7deedf9 in Gtk::Button::on_clicked() ()
   from /usr/lib/i386-linux-gnu/libgtkmm-2.4.so.1
#12 0xb7def2eb in Gtk::Button_Class::clicked_callback(_GtkButton*) ()
   from /usr/lib/i386-linux-gnu/libgtkmm-2.4.so.1
#13 0xb71af5da in g_cclosure_marshal_VOID__VOIDv ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#14 0xb71ac177 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#15 0xb71adad1 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#16 0xb71c6e77 in g_signal_emit_valist ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#17 0xb71c78b3 in g_signal_emit ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#18 0xb759c26a in gtk_button_clicked ()
   from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
#19 0xb7736528 in ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
#20 0xb7deee59 in Gtk::Button::on_released() ()
   from /usr/lib/i386-linux-gnu/libgtkmm-2.4.so.1
#21 0xb7def3ab in Gtk::Button_Class::released_callback(_GtkButton*) ()
   from /usr/lib/i386-linux-gnu/libgtkmm-2.4.so.1
#22 0xb71af5da in g_cclosure_marshal_VOID__VOIDv ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#23 0xb71ac177 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#24 0xb71adad1 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#25 0xb71c6e77 in g_signal_em...

[su_v (suv-lp)]

Based on the Inkscape version (taken from the file, since it was not mentioned in the report):
> inkscape:version="0.48.3.1 r9886"
 and the id of <sodipodi:namedview> of the provided sample file:
> id="namedview3041"
this is another duplicate of a known regression in Inkscape 0.48.3.1:

Linking as duplicate to
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>