Bug 1623516

Summary: [abrt] inkscape: Inkscape::XML::SimpleNode::removeChild(Inkscape::XML::Node*)(): inkscape killed by SIGABRT
Product: [Fedora] Fedora Reporter: D. Stimits <stimits>
Component: inkscapeAssignee: Gwyn Ciesla <gwync>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: duffy, gwync, jonathan.underwood, lkundrak, rlerch
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/255275f3cb4d28bd049afdfe0382247da115ccab
Whiteboard: abrt_hash:3559043d66ccf79eff9d5d3c07cfe7bc0de50c04;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 22:27:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: bug_personal_check.svg
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description D. Stimits 2018-08-29 14:16:36 UTC
Description of problem:
1. The page size was previously set to match the graphics content.
2. The object was skewed -1 degree (it was supposed to be a minor tweak).
3. Again the page size was set to match the graphics content.
   A. This resulted in a bug where the page wasn't actually
      matching the object. Instead there was extra white
      space at the bottom. This is the actual start of something
      gone corrupt.
3. "edit "undo" of the bugged matching of page size to
   object results in the crash every time.
   A. Apparently it isn't possible to undo a custom page size
      setting when something went wrong and the page size didn't
      actually change.
   B. Inkscape's GUI made it look like the vertical height of
      the object grew by adding white space to the bottom.
      Different parts of Inkscape apparently had different
      (conflicting) ideas of the object's size.

Version-Release number of selected component:
inkscape-0.92.3-2.fc27

Additional info:
reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        inkscape
crash_function: Inkscape::XML::SimpleNode::removeChild(Inkscape::XML::Node*)
executable:     /usr/bin/inkscape
journald_cursor: s=bbde8b6fce0c41cfb977b132d339a947;i=6ae3e;b=6219bee56d2e4a6a97f87a791d556be9;m=10a6526b9;t=5749354692b09;x=abef7fd7c13fba02
kernel:         4.17.14-102.fc27.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #4 Inkscape::XML::SimpleNode::removeChild(Inkscape::XML::Node*) at /usr/src/debug/inkscape-0.92.3-2.fc27.x86_64/src/xml/simple-node.cpp:457
 #5 Inkscape::XML::Event::undoOne(Inkscape::XML::NodeObserver&) const at /usr/src/debug/inkscape-0.92.3-2.fc27.x86_64/src/xml/event.h:103
 #6 Inkscape::XML::undo_log_to_observer(Inkscape::XML::Event const*, Inkscape::XML::NodeObserver&) at /usr/src/debug/inkscape-0.92.3-2.fc27.x86_64/src/xml/event.cpp:131
 #7 sp_repr_undo_log(Inkscape::XML::Event*) at /usr/src/debug/inkscape-0.92.3-2.fc27.x86_64/src/xml/event.cpp:149
 #8 Inkscape::DocumentUndo::undo(SPDocument*) at /usr/src/debug/inkscape-0.92.3-2.fc27.x86_64/src/document-undo.cpp:265
 #9 sp_undo(SPDesktop*, SPDocument*) at /usr/src/debug/inkscape-0.92.3-2.fc27.x86_64/src/selection-chemistry.cpp:1228
 #10 sigc::internal::signal_emit0<void, sigc::nil>::emit(sigc::internal::signal_impl*) at /usr/include/sigc++-2.0/sigc++/signal.h:794
 #11 sigc::signal0<void, sigc::nil>::emit() const at /usr/include/sigc++-2.0/sigc++/signal.h:2800
 #12 sp_action_perform(SPAction*, void*) at /usr/src/debug/inkscape-0.92.3-2.fc27.x86_64/src/helper/action.cpp:136

Comment 1 D. Stimits 2018-08-29 14:16:42 UTC
Created attachment 1479499 [details]
File: backtrace

Comment 2 D. Stimits 2018-08-29 14:16:44 UTC
Created attachment 1479500 [details]
File: bug_personal_check.svg

Comment 3 D. Stimits 2018-08-29 14:16:45 UTC
Created attachment 1479501 [details]
File: cgroup

Comment 4 D. Stimits 2018-08-29 14:16:46 UTC
Created attachment 1479502 [details]
File: core_backtrace

Comment 5 D. Stimits 2018-08-29 14:16:47 UTC
Created attachment 1479503 [details]
File: cpuinfo

Comment 6 D. Stimits 2018-08-29 14:16:47 UTC
Created attachment 1479504 [details]
File: dso_list

Comment 7 D. Stimits 2018-08-29 14:16:48 UTC
Created attachment 1479505 [details]
File: environ

Comment 8 D. Stimits 2018-08-29 14:16:49 UTC
Created attachment 1479506 [details]
File: limits

Comment 9 D. Stimits 2018-08-29 14:16:50 UTC
Created attachment 1479507 [details]
File: maps

Comment 10 D. Stimits 2018-08-29 14:16:51 UTC
Created attachment 1479508 [details]
File: mountinfo

Comment 11 D. Stimits 2018-08-29 14:16:52 UTC
Created attachment 1479509 [details]
File: open_fds

Comment 12 D. Stimits 2018-08-29 14:16:53 UTC
Created attachment 1479510 [details]
File: proc_pid_status

Comment 13 Ben Cotton 2018-11-27 14:44:20 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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' of '27'.

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 27 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.

Comment 14 Ben Cotton 2018-11-30 22:27:38 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.