Bug 1742898

Summary: [abrt] kicad: poll_for_event(): kicad killed by SIGABRT
Product: [Fedora] Fedora Reporter: Florian Alber <albflo>
Component: kicadAssignee: Chitlesh GOORAH <chitlesh>
Status: CLOSED DEFERRED QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: aimylios, chitlesh, kiarakovalevsky, stevenfalco, thibault.north
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2445efe4956bb8c4103c7a92abb405e02e18afc3
Whiteboard: abrt_hash:930647579125cfde0a6a591de9c6d6c1f3e91b77;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 14:35:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ none

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.