Red Hat Bugzilla – Bug 1303310
[abrt] inkscape: issueClearUndo(): inkscape killed by SIGSEGV
Last modified: 2016-07-19 14:41:46 EDT
Description of problem:
1. I open a svg file in Inkscape.
2. At the same time I edit the file with the vim editor.
3. After saving some changes, I reload the file in Inkscape (File -> Revert)
4. Inkscape crashed upon trying to reload.
It happened a couple of times earlier today, but this time I think I noticed what I expect is triggering it. I was using the "Edit paths by nodes" tool, and had selected a node, e.g. the control point lines were showing. The edit of the file changed one of those control points, I assume the crash is related to that.
Version-Release number of selected component:
cmdline: inkscape 'fra_bunnen_h\xc3\xa5ndlaget.svg'
runlevel: N 5
Thread no. 1 (10 frames)
#1 issueClearUndo at composite-undo-stack-observer.h:92
#2 Inkscape::CompositeUndoStackObserver::notifyClearUndoEvent at composite-undo-stack-observer.cpp:86
#3 Inkscape::DocumentUndo::clearUndo at document-undo.cpp:328
#4 SPDocument::~SPDocument at document.cpp:164
#6 Inkscape::UI::View::View::setDocument at ui/view/view.cpp:116
#7 SPDesktop::setDocument at desktop.cpp:1596
#8 SPDesktop::change_document at desktop.cpp:663
#9 sp_file_open at file.cpp:297
#10 sp_file_revert_dialog at file.cpp:381
#11 emit at /usr/include/sigc++-2.0/sigc++/signal.h:772
Potential duplicate: bug 1189070
Created attachment 1119644 [details]
Created attachment 1119645 [details]
Created attachment 1119646 [details]
Created attachment 1119647 [details]
Created attachment 1119648 [details]
Created attachment 1119649 [details]
Created attachment 1119650 [details]
Created attachment 1119651 [details]
Created attachment 1119652 [details]
Created attachment 1119653 [details]
Created attachment 1119654 [details]
Created attachment 1119655 [details]
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.