Bug 700578

Summary: [abrt] gcompris-9.5-1.fc14: g_object_notify_queue_free: Process /usr/bin/gcompris was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Catalin BOIE <fedora-bugzilla>
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: i686   
OS: Unspecified   
Whiteboard: abrt_hash:1acc47f9c42d6998f8cc82bb29b9ed0823492065
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-09 07:54:04 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 Catalin BOIE 2011-04-28 17:35:16 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 49669 bytes
cmdline: gcompris
component: gcompris
Attached file: coredump, 83267584 bytes
crash_function: g_object_notify_queue_free
executable: /usr/bin/gcompris
kernel: 2.6.35.12-88.fc14.i686.PAE
package: gcompris-9.5-1.fc14
rating: 4
reason: Process /usr/bin/gcompris was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302366235
uid: 503

How to reproduce
-----
1. My 4 years old kid triggered it. I really do not know what happened.
2.
3.
Comment 1 Catalin BOIE 2011-04-28 17:35:18 UTC 
Created attachment 495613 [details]
File: backtrace
Comment 2 Hans de Goede 2011-12-09 07:54:04 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