Description of problem: I used the Fill bounded areas 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=1c55d76d207442e0a536e2d84ed7cb8f;i=b3fd;b=f7d5820df9264049a17de11047fa1d63;m=158c0495a;t=56e776824dfec;x=12d039aaddb33534 kernel: 4.16.14-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1451593 [details] File: backtrace
Created attachment 1451594 [details] File: cgroup
Created attachment 1451595 [details] File: core_backtrace
Created attachment 1451596 [details] File: cpuinfo
Created attachment 1451597 [details] File: dso_list
Created attachment 1451598 [details] File: environ
Created attachment 1451599 [details] File: limits
Created attachment 1451600 [details] File: maps
Created attachment 1451601 [details] File: mountinfo
Created attachment 1451602 [details] File: open_fds
Created attachment 1451603 [details] File: proc_pid_status
Created attachment 1451604 [details] File: var_log_messages
The problem persist: - inkscape.x86_64-0.92.3-2.fc28 - from official fedora repository, @updates - Fedora Workstation 28
Interesting, inscape from flatpak works fine. - version: stable - source: dl.flathub.org my real download speed is 640KiB/s, it took me 8 minutes 24 seconds to install by flatpak, in general flatpak always take me long time compared to official repositories.
*** Bug 1624569 has been marked as a duplicate of this bug. ***
(In reply to christianbueno from comment #14) > Interesting, inscape from flatpak works fine. > - version: stable > - source: dl.flathub.org > > my real download speed is 640KiB/s, it took me 8 minutes 24 seconds to > install by flatpak, in general flatpak always take me long time compared to > official repositories. Completely removed my inkscap install, removed all related config files, installed the flatpak version from flathub repo, error persists for me.
Similar problem has been detected: Tried to use "Fill bounded area" tool. The fill color probably wasn't selected. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/inkscape crash_function: std::__replacement_assert executable: /usr/bin/inkscape journald_cursor: s=2e3773c6b7984e72b9a7709e89e568bd;i=187401;b=0b66527047d74424a2e0355613e0ad80;m=1400edf55f;t=5817172f77388;x=cb2cf4b1c3389e18 kernel: 4.20.6-100.fc28.x86_64 package: inkscape-0.92.3-2.fc28 reason: inkscape killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1224
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.