Description of problem: Inkscape unpredictably crashes on (almost) any path operation. To reproduce this particular case: 1. Create any two paths/rectangles/circles/whatever 2. Apply division on them Version-Release number of selected component: inkscape-0.92.3-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: inkscape crash_function: std::__replacement_assert executable: /usr/bin/inkscape journald_cursor: s=3caf0b7f83c74091955fac4f73bb185b;i=119dfa;b=7fc2bc746a0c4f1e99c869861d51331e;m=129b09244;t=56e90e3d3e5c1;x=c65d2a8bc3eca9a kernel: 4.16.14-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1451086 [details] File: backtrace
Created attachment 1451087 [details] File: cgroup
Created attachment 1451088 [details] File: core_backtrace
Created attachment 1451089 [details] File: cpuinfo
Created attachment 1451090 [details] File: dso_list
Created attachment 1451091 [details] File: environ
Created attachment 1451092 [details] File: limits
Created attachment 1451093 [details] File: maps
Created attachment 1451094 [details] File: mountinfo
Created attachment 1451095 [details] File: open_fds
Created attachment 1451096 [details] File: proc_pid_status
Created attachment 1451097 [details] File: var_log_messages
Similar problem has been detected: I was doing path division of two squares. Bigger black one divided by small red, if it helps :) reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: inkscape crash_function: std::__replacement_assert executable: /usr/bin/inkscape journald_cursor: s=9ff9044c994848d9814e5ed67f2ae745;i=78530;b=ffd2ac4a2f5f4cd9aa1e648e7416d5ad;m=e3581354;t=57289035b5a42;x=83259ce522a1f9ee kernel: 4.17.7-200.fc28.x86_64 package: inkscape-0.92.3-2.fc28 reason: inkscape killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.