Bug 2079984 - [abrt] kicad: std::__replacement_assert(): kicad killed by SIGABRT
Summary: [abrt] kicad: std::__replacement_assert(): kicad killed by SIGABRT
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kicad
Version: 34
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Geoffrey Marr
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:87cd97cc63b828419ceaf4bb031...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-28 16:55 UTC by abode091@gmail.com
Modified: 2022-05-04 12:54 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-05-04 12:54:12 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (146.52 KB, text/plain)
2022-04-28 16:55 UTC, abode091@gmail.com 		no flags Details
File: core_backtrace (58.31 KB, text/plain)
2022-04-28 16:55 UTC, abode091@gmail.com 		no flags Details
File: cpuinfo (2.42 KB, text/plain)
2022-04-28 16:55 UTC, abode091@gmail.com 		no flags Details
File: dso_list (252 bytes, text/plain)
2022-04-28 16:55 UTC, abode091@gmail.com 		no flags Details
File: environ (1.70 KB, text/plain)
2022-04-28 16:55 UTC, abode091@gmail.com 		no flags Details
File: limits (1.29 KB, text/plain)
2022-04-28 16:55 UTC, abode091@gmail.com 		no flags Details
File: maps (3.96 KB, text/plain)
2022-04-28 16:55 UTC, abode091@gmail.com 		no flags Details
File: mountinfo (2.84 KB, text/plain)
2022-04-28 16:55 UTC, abode091@gmail.com 		no flags Details
File: open_fds (2.59 KB, text/plain)
2022-04-28 16:55 UTC, abode091@gmail.com 		no flags Details
File: proc_pid_status (1.38 KB, text/plain)
2022-04-28 16:55 UTC, abode091@gmail.com 		no flags Details
View All

Description abode091@gmail.com 2022-04-28 16:55:27 UTC 
Version-Release number of selected component:
kicad-1:6.0.4-1.fc34

Additional info:
reporter:       libreport-2.15.2
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-glib-kicad-4258.scope
cmdline:        kicad
crash_function: std::__replacement_assert
executable:     /usr/bin/kicad
journald_cursor: s=e52d416e20674e4bac4122a7f48da430;i=44fe6;b=75173928808f432c9093aa3c518c4468;m=715436cd;t=5ddb850463b6d;x=3c774e9b08332ed5
kernel:         5.17.4-100.fc34.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 abode091@gmail.com 2022-04-28 16:55:32 UTC 
Created attachment 1875722 [details]
File: backtrace
Comment 2 abode091@gmail.com 2022-04-28 16:55:34 UTC 
Created attachment 1875723 [details]
File: core_backtrace
Comment 3 abode091@gmail.com 2022-04-28 16:55:35 UTC 
Created attachment 1875724 [details]
File: cpuinfo
Comment 4 abode091@gmail.com 2022-04-28 16:55:36 UTC 
Created attachment 1875725 [details]
File: dso_list
Comment 5 abode091@gmail.com 2022-04-28 16:55:37 UTC 
Created attachment 1875726 [details]
File: environ
Comment 6 abode091@gmail.com 2022-04-28 16:55:39 UTC 
Created attachment 1875727 [details]
File: limits
Comment 7 abode091@gmail.com 2022-04-28 16:55:41 UTC 
Created attachment 1875728 [details]
File: maps
Comment 8 abode091@gmail.com 2022-04-28 16:55:42 UTC 
Created attachment 1875729 [details]
File: mountinfo
Comment 9 abode091@gmail.com 2022-04-28 16:55:44 UTC 
Created attachment 1875730 [details]
File: open_fds
Comment 10 abode091@gmail.com 2022-04-28 16:55:45 UTC 
Created attachment 1875731 [details]
File: proc_pid_status
Comment 11 Steven A. Falco 2022-04-29 13:11:07 UTC 
Can you please describe what you were doing when the crash occurred?  Can you reproduce the problem?
Comment 12 abode091@gmail.com 2022-05-04 08:50:16 UTC 
I don't think I can reduce the problem, it happened only once, I think I was opening PCBnew to make some changes
I did that a lot, it only crashed this one time.

I'm sorry I think I can't provide more information other than what's included in the report

thanks a lot.
Comment 13 Steven A. Falco 2022-05-04 12:54:12 UTC 
Thanks for reporting it.  I'll close this bug for now, but if you find a way to reproduce it, then please reopen the bug.  The KiCad team are very responsive.
Note You need to log in before you can comment on or make changes to this bug.