Inkscape catches SIGSEGV when I try to fill out a figure

[anesth]

System: 0-day 64-bit Gentoo Linux. CPU: Intel C2 Duo T6570.

1. (of course) Launch Inkscape.
2. Draw any figure. Select it.
3. Open "Object"->"Fill and Stroke" panel (Ctrl-Shift-F)
4. Click on colour chooser to fill out the figure.
That's all, Inkscape crashes.

gdb says:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7c676a8 in ?? ()
(gdb) bt
#0 0x00007ffff7c676a8 in ?? ()
#1 0x00007ffff35de0ba in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#2 0x00007ffff35f868e in ?? () from /usr/lib/libgobject-2.0.so.0
#3 0x00007ffff35f9bc9 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#4 0x00007ffff35fa183 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#5 0x00007ffff35de0ba in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#6 0x00007ffff35f868e in ?? () from /usr/lib/libgobject-2.0.so.0
#7 0x00007ffff35f9bc9 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#8 0x00007ffff35fa183 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#9 0x00007ffff76843f6 in ?? ()
#10 0x00007ffff76845ca in ?? ()
#11 0x00007ffff32ff029 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#12 0x00007ffff3303ab8 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0x00007ffff3304025 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#14 0x00007ffff4cfb957 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#15 0x00007ffff7637775 in ?? ()
#16 0x00007ffff7636ab1 in main ()

[su_v (suv-lp)]

> 64-bit Gentoo Linux

Possibly same crash as reported in
Bug #629363 “inkscape 0.48 crashes in sp_stroke_style_line_update() when drawing with opened "Fill and Stroke" dialog”
<https://bugs.launchpad.net/inkscape/+bug/629363>

(unfortunately your backtrace doesn't provide information where the crash in Inkscape happens).

[jazzynico (jazzynico)]

Marking duplicate of Bug #629363 “inkscape 0.48 crashes in sp_stroke_style_line_update() when drawing with opened "Fill and Stroke" dialog”
<https://bugs.launchpad.net/inkscape/+bug/629363>

Should be fixed in 0.48.2. Don't hesitate to comment and revert the report's status of you run into the same issue again with a recent Inskcape version.