Bug 1591483 - [abrt] inkscape: std::__replacement_assert(): inkscape killed by SIGABRT
Summary: [abrt] inkscape: std::__replacement_assert(): inkscape killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: inkscape
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:7b6b6fdb8c99d3a60b706a95bfe...
: 1624569 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-14 20:28 UTC by Aram
Modified: 2019-05-28 23:39 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 23:39:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (200.40 KB, text/plain)
2018-06-14 20:28 UTC, Aram
no flags Details
File: cgroup (331 bytes, text/plain)
2018-06-14 20:28 UTC, Aram
no flags Details
File: core_backtrace (34.62 KB, text/plain)
2018-06-14 20:28 UTC, Aram
no flags Details
File: cpuinfo (1.16 KB, text/plain)
2018-06-14 20:28 UTC, Aram
no flags Details
File: dso_list (12.71 KB, text/plain)
2018-06-14 20:28 UTC, Aram
no flags Details
File: environ (3.65 KB, text/plain)
2018-06-14 20:28 UTC, Aram
no flags Details
File: limits (1.29 KB, text/plain)
2018-06-14 20:28 UTC, Aram
no flags Details
File: maps (64.19 KB, text/plain)
2018-06-14 20:29 UTC, Aram
no flags Details
File: mountinfo (3.68 KB, text/plain)
2018-06-14 20:29 UTC, Aram
no flags Details
File: open_fds (681 bytes, text/plain)
2018-06-14 20:29 UTC, Aram
no flags Details
File: proc_pid_status (1.31 KB, text/plain)
2018-06-14 20:29 UTC, Aram
no flags Details
File: var_log_messages (721 bytes, text/plain)
2018-06-14 20:29 UTC, Aram
no flags Details

Description Aram 2018-06-14 20:28:42 UTC
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

Comment 1 Aram 2018-06-14 20:28:49 UTC
Created attachment 1451593 [details]
File: backtrace

Comment 2 Aram 2018-06-14 20:28:50 UTC
Created attachment 1451594 [details]
File: cgroup

Comment 3 Aram 2018-06-14 20:28:52 UTC
Created attachment 1451595 [details]
File: core_backtrace

Comment 4 Aram 2018-06-14 20:28:54 UTC
Created attachment 1451596 [details]
File: cpuinfo

Comment 5 Aram 2018-06-14 20:28:56 UTC
Created attachment 1451597 [details]
File: dso_list

Comment 6 Aram 2018-06-14 20:28:57 UTC
Created attachment 1451598 [details]
File: environ

Comment 7 Aram 2018-06-14 20:28:58 UTC
Created attachment 1451599 [details]
File: limits

Comment 8 Aram 2018-06-14 20:29:00 UTC
Created attachment 1451600 [details]
File: maps

Comment 9 Aram 2018-06-14 20:29:02 UTC
Created attachment 1451601 [details]
File: mountinfo

Comment 10 Aram 2018-06-14 20:29:03 UTC
Created attachment 1451602 [details]
File: open_fds

Comment 11 Aram 2018-06-14 20:29:04 UTC
Created attachment 1451603 [details]
File: proc_pid_status

Comment 12 Aram 2018-06-14 20:29:06 UTC
Created attachment 1451604 [details]
File: var_log_messages

Comment 13 christianbueno 2018-08-22 18:18:56 UTC
The problem persist:
- inkscape.x86_64-0.92.3-2.fc28
- from official fedora repository, @updates
- Fedora Workstation 28

Comment 14 christianbueno 2018-08-22 20:18:26 UTC
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.

Comment 15 Roman Hodain 2018-09-01 15:34:56 UTC
*** Bug 1624569 has been marked as a duplicate of this bug. ***

Comment 16 Willdrick 2019-02-07 13:53:39 UTC
(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.

Comment 17 Pawel Veselov 2019-02-09 08:11:24 UTC
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

Comment 18 Ben Cotton 2019-05-02 19:18:22 UTC
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.

Comment 19 Ben Cotton 2019-05-02 19:56:03 UTC
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.

Comment 20 Ben Cotton 2019-05-28 23:39:03 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.