Bug 672340

Summary: [abrt] rhythmbox-0.13.2-1.fc14: g_object_unref: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: majhoul <majhoul>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: bdpepple, bnocera, stedchris
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:c70469847a59bb0c1657b15583bcc825fb34f507
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 17:46:34 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 majhoul 2011-01-24 21:32:55 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: rhythmbox
component: rhythmbox
crash_function: g_object_unref
executable: /usr/bin/rhythmbox
kernel: 2.6.35.10-74.fc14.i686
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: 1295903375
uid: 500

How to reproduce
-----
1. Start Rhythmbox
2. While loading the database, double click on "Last.fm"
3. Crash
Comment 1 majhoul 2011-01-24 21:32:58 UTC 
Created attachment 475053 [details]
File: backtrace
Comment 2 cstent 2011-01-28 13:18:59 UTC 
Package: rhythmbox-0.13.2-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.just tried to start it
2.
3.
Comment 3 Brian Pepple 2011-01-31 01:42:23 UTC 
Package: rhythmbox-0.13.2-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Opened Rhythmbox
2. Crashed while checking checking music files on start-up.
Comment 4 abrt-bot 2012-03-21 17:46:34 UTC 
Backtrace analysis found this bug to be similar to bug #700991, closing as duplicate.

Bugs which were found to be similar to this bug: bug #683306, bug #700991

This comment is automatically generated.

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