Bug 695352

Summary: [abrt] gcompris-9.5-1.fc14: gc_db_board_update: Process /usr/bin/gcompris was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Raúl Giucich <raul.giucich>
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:ba38c6354d992e9a0dfc0b2de7a17e5fa23566c2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-09 07:53:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Raúl Giucich 2011-04-11 12:59:43 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 20556 bytes
cmdline: gcompris -a --nolockcheck
component: gcompris
Attached file: coredump, 18800640 bytes
crash_function: gc_db_board_update
executable: /usr/bin/gcompris
kernel: 2.6.35.11-83.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: 1302184157
uid: 500

How to reproduce
-----
1. n/a
2.
3.
Comment 1 Raúl Giucich 2011-04-11 12:59:46 UTC 
Created attachment 491230 [details]
File: backtrace
Comment 2 Hans de Goede 2011-12-09 07:53:56 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