Bug 740281

Summary: [abrt] gcompris-9.5-1.fc14: __libc_message: Process /usr/bin/gcompris was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Richard Ryniker <ryniker>
Component: gcomprisAssignee: Hans de Goede <hdegoede>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: gwync, hdegoede
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:30f13e619335a99e3fbb1c919d64b6ca12dbe481
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-09 07:54:14 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

Description Richard Ryniker 2011-09-21 14:16:51 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 33268 bytes
cmdline: gcompris
component: gcompris
Attached file: coredump, 120557568 bytes
crash_function: __libc_message
executable: /usr/bin/gcompris
kernel: 2.6.35.13-92.fc14.x86_64
package: gcompris-9.5-1.fc14
rating: 4
reason: Process /usr/bin/gcompris was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1316613666
uid: 501

How to reproduce
-----
1. CTRL-q  to terminate gcompris  (chess game)
2.
3.
Comment 1 Richard Ryniker 2011-09-21 14:16:54 UTC 
Created attachment 524206 [details]
File: backtrace
Comment 2 Hans de Goede 2011-12-09 07:54:14 UTC 
Hi,

Thanks for the bug report, and sorry it took so long for me to get around to looking into this. Looking at the backtrace unfortunately does not give any clues what might be the cause of this crash. And since no-one else has reported a bug with a similar backtrace this bug seems to happen almost never / is almost impossible to reproduce. Therefor I see no other option then to close this bug.

Regards,

Hans
Comment 3 Richard Ryniker 2011-12-09 12:35:17 UTC 
I no longer see the failure.  There have been (at least two) kernel builds, and maintenance to GTK, since abrt recorded the gcompris failure.  It is likely something outside gcompris caused the problem.