Bug 700578 - [abrt] gcompris-9.5-1.fc14: g_object_notify_queue_free: Process /usr/bin/gcompris was killed by signal 11 (SIGSEGV)
Summary: [abrt] gcompris-9.5-1.fc14: g_object_notify_queue_free: Process /usr/bin/gcom...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gcompris
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1acc47f9c42d6998f8cc82bb29b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-28 17:35 UTC by Catalin BOIE
Modified: 2011-12-09 07:54 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
File: backtrace (48.50 KB, text/plain)
2011-04-28 17:35 UTC, Catalin BOIE 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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