Bug 669886

Summary: [abrt] rhythmbox-0.13.2-1.fc14: g_type_check_instance_cast: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: shashank <shashank.neelam>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: bnocera, fybanez
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:7d0a82cf0c64ee2a6478bd239b433c82852534b7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 16:30:03 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 shashank 2011-01-15 14:28:15 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: rhythmbox
component: rhythmbox
crash_function: g_type_check_instance_cast
executable: /usr/bin/rhythmbox
kernel: 2.6.35.10-74.fc14.x86_64
package: rhythmbox-0.13.2-1.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1295096690
uid: 500

How to reproduce
-----
1. font know
2.
3.
Comment 1 shashank 2011-01-15 14:28:17 UTC 
Created attachment 473643 [details]
File: backtrace
Comment 2 Frank Ybanez 2011-01-21 01:25:51 UTC 
Package: rhythmbox-0.13.2-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Just siting in front of the computer (seriously).
2.
3.


Comment
-----
The app had been running for some 20 or so hours, something gave the following day, when I attempted to resume my use of it again.
Comment 3 abrt-bot 2012-03-21 16:30:03 UTC 
Backtrace analysis found this bug to be similar to bug #681381, closing as duplicate.

Bugs which were found to be similar to this bug: bug #681381, bug #766129

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 681381 ***