Inkscape-0.39 has a crash in the fill/stroke dialogs caused by following a pointer from a destroyed object. The bug is hidden in glib-2.4 because of less aggressive memory freeing behaviour. The fix is already in inkscape CVS, at http://cvs.sourceforge.net/viewcvs.py/inkscape/inkscape/src/sp-object.cpp?r1=1.45&r2=1.46&diff_format=u
Inkscape 0.40 fixes this problem (see the first comment). Therefore adding the ebuild posted in the "Inkskape 0.40 is out"-bug report fixes this bugreport.
As 0.40 is in the tree, I think this can be closed.