Red Hat Bugzilla – Bug 1467594
[abrt] inkscape: Inkscape::ObjectSet::_clear(): inkscape killed by SIGSEGV
Last modified: 2017-12-12 05:26:51 EST
Description of problem:
0. I am running fedora with xfce , and using workspace switcher with 24 workspaces.
I have been using this arrangement for a year or so to generate very large & complex inkscape documents.
recently upgraded to F25, but crashes did NOT begin immediately after upgrade.
Once the crashes began, with no obvious trigger, I dnf updated everything -- but crashes continued.
1. bring up inkscape by clicking on launcher. so it is editing a blank document.
2. select text tool and type "Hello, World!"
3. click on background to deselect text.
4. BOOM -- crash happens, and close button appears.
5. I can't click on close button because window manager is locked up, but I can switch to a different
workspace with ctrl-F6, and then get back to this workspace, and then click close.
6. Gaze at screen with sorrow, because my friend Inkscape has died.
Version-Release number of selected component:
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor: Fedora Project
runlevel: N 5
Thread no. 1 (10 frames)
#0 Inkscape::ObjectSet::_clear at /usr/src/debug/inkscape-r15686/src/object-set.cpp:124
#1 Inkscape::ObjectSet::clear at /usr/src/debug/inkscape-r15686/src/object-set.cpp:75
#2 Inkscape::UI::Tools::SelectTool::root_handler at /usr/src/debug/inkscape-r15686/src/ui/tools/select-tool.cpp:767
#3 Inkscape::UI::Tools::sp_event_context_virtual_root_handler at /usr/src/debug/inkscape-r15686/src/ui/tools/tool-base.cpp:1020
#4 Inkscape::UI::Tools::sp_event_context_root_handler at /usr/src/debug/inkscape-r15686/src/ui/tools/tool-base.cpp:1008
#5 sp_desktop_root_handler at /usr/src/debug/inkscape-r15686/src/desktop-events.cpp:86
#6 sp_marshal_BOOLEAN__POINTER at /usr/src/debug/inkscape-r15686/src/helper/sp-marshal.cpp:124
#11 SPCanvas::emitEvent at /usr/src/debug/inkscape-r15686/src/display/sp-canvas.cpp:1258
#12 SPCanvas::handle_button at /usr/src/debug/inkscape-r15686/src/display/sp-canvas.cpp:1453
#13 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:143
Created attachment 1294137 [details]
Created attachment 1294138 [details]
Created attachment 1294139 [details]
Created attachment 1294140 [details]
Created attachment 1294141 [details]
Created attachment 1294142 [details]
Created attachment 1294143 [details]
Created attachment 1294144 [details]
Created attachment 1294145 [details]
Created attachment 1294146 [details]
Created attachment 1294148 [details]
Created attachment 1294149 [details]
Created attachment 1294150 [details]
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.