Bug 1742898 - [abrt] kicad: poll_for_event(): kicad killed by SIGABRT
Summary: [abrt] kicad: poll_for_event(): kicad killed by SIGABRT
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: kicad
Version: 30
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Chitlesh GOORAH
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:930647579125cfde0a6a591de9c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-17 12:33 UTC by Florian Alber
Modified: 2019-08-19 14:35 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 14:35:00 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (38.37 KB, text/plain)
2019-08-17 12:33 UTC, Florian Alber 		no flags Details
File: cgroup (331 bytes, text/plain)
2019-08-17 12:33 UTC, Florian Alber 		no flags Details
File: core_backtrace (14.64 KB, text/plain)
2019-08-17 12:33 UTC, Florian Alber 		no flags Details
File: cpuinfo (1.47 KB, text/plain)
2019-08-17 12:33 UTC, Florian Alber 		no flags Details
File: dso_list (20.23 KB, text/plain)
2019-08-17 12:33 UTC, Florian Alber 		no flags Details
File: environ (3.83 KB, text/plain)
2019-08-17 12:33 UTC, Florian Alber 		no flags Details
View All

Description Florian Alber 2019-08-17 12:33:20 UTC 
Description of problem:
Hi,

after starting my pcb project, I loaded the configuration from my schematics file and afterwards I wanted to
open the properties of one footprint. I didn't really realise if Kicad shut down when I hit the right mouse button
or if it stoped when I draged the part.

Best,
albflo

Version-Release number of selected component:
1:kicad-5.1.2-1.fc30

Additional info:
reporter:       libreport-2.10.1
backtrace_rating: 3
cmdline:        kicad
crash_function: poll_for_event
executable:     /usr/bin/kicad
journald_cursor: s=eca44f3cb0a7473fb7fe023ce2094782;i=3bd56;b=56a54117686f47ee80104f993cba2a1a;m=21fe19ac1;t=5904ebc766ab3;x=1bce54448bac49c8
kernel:         5.2.8-200.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 Florian Alber 2019-08-17 12:33:25 UTC 
Created attachment 1605263 [details]
File: backtrace
Comment 2 Florian Alber 2019-08-17 12:33:26 UTC 
Created attachment 1605264 [details]
File: cgroup
Comment 3 Florian Alber 2019-08-17 12:33:28 UTC 
Created attachment 1605265 [details]
File: core_backtrace
Comment 4 Florian Alber 2019-08-17 12:33:33 UTC 
Created attachment 1605266 [details]
File: cpuinfo
Comment 5 Florian Alber 2019-08-17 12:33:35 UTC 
Created attachment 1605267 [details]
File: dso_list
Comment 6 Florian Alber 2019-08-17 12:33:37 UTC 
Created attachment 1605268 [details]
File: environ
Comment 7 Steven A. Falco 2019-08-17 16:13:57 UTC 
I forwarded your report to the KiCAD developers, but they tell me there is not enough information in the backtrace to figure out what is going on.

If you have a way to reproduce the issue, then we can work on it.

Please let us know.
Comment 8 Florian Alber 2019-08-19 06:08:27 UTC 
Hi Steven,

no I can't reproduce it, so probably it was a random crash of KiCAD.

Thank you!
Best,
albflo
Comment 9 Steven A. Falco 2019-08-19 14:35:00 UTC 
Ok - I'll close this bug for now, but if you do find a way to make it happen please let us know.
Note You need to log in before you can comment on or make changes to this bug.