Bug 683662

Summary: [abrt] gcompris-9.3-3.fc14: gc_board_stop: Process /usr/bin/gcompris was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jesse B <nebulous1>
Component: gcomprisAssignee: Hans de Goede <hdegoede>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: gwync, hdegoede
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:8e8a854fb491c07ca935578d16e6ae91e73e4129
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-11 19:41:15 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 Jesse B 2011-03-09 23:44:50 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 49382 bytes
cmdline: gcompris
comment: I recently removed the 'rhgb quiet' args from grub.conf.  Doesn't seem related, but mentioning it just the same.
component: gcompris
Attached file: coredump, 54042624 bytes
crash_function: gc_board_stop
executable: /usr/bin/gcompris
kernel: 2.6.35.11-83.fc14.i686
package: gcompris-9.3-3.fc14
rating: 4
reason: Process /usr/bin/gcompris was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299710280
uid: 502

How to reproduce
-----
1.  Just trying to start GCompris Educational suite, which normally runs just fine.  This time it crashed when I tried to start it.
2.
3.

Comment 1 Jesse B 2011-03-09 23:44:53 UTC
Created attachment 483323 [details]
File: backtrace

Comment 2 Hans de Goede 2011-03-11 19:41:15 UTC
Hi,

Thanks for the bug report! 9.3 is a bit old, we've had 9.5 in updates-testing for quite a while now. I've just pushed it to the stable updates repository. So it should be available as an update to F-14 in circa 24 hours. If you hit the same (or another) problem with this new version, please file another bug using abrt (so that we get a backtrace from the new version).

Thanks & Regards,

Hans