Bug 695352 - [abrt] gcompris-9.5-1.fc14: gc_db_board_update: Process /usr/bin/gcompris was killed by signal 6 (SIGABRT)
Summary: [abrt] gcompris-9.5-1.fc14: gc_db_board_update: Process /usr/bin/gcompris was...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gcompris
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ba38c6354d992e9a0dfc0b2de7a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-11 12:59 UTC by Raúl Giucich
Modified: 2011-12-09 07:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-09 07:53:56 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (20.07 KB, text/plain)
2011-04-11 12:59 UTC, Raúl Giucich 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.