Bug 658454

Summary: [abrt] rhythmbox-0.13.1-2.fc14: g_object_unref: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: florin.smeu
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, vadim2071
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:401a4a09c6f5135b6f6a35b4e0a60ecb95d13b29
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 17:55:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description florin.smeu 2010-11-30 12:41:37 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.6-48.fc14.i686
package: rhythmbox-0.13.1-2.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1291119945
uid: 1000

How to reproduce
-----
1. Right click on "listen.pls" paylist file and select "Open with Rhythmbox" while Rhythmbox is already running;
2. Rhythmbox crashes.
Comment 1 florin.smeu 2010-11-30 12:41:40 UTC 
Created attachment 463708 [details]
File: backtrace
Comment 2 Vadim 2010-12-24 06:53:46 UTC 
Package: rhythmbox-0.13.1-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.
3.
I wonted run rhythmbox http://www.hitroe.com:8000/stream.m3u
:)
Comment 3 abrt-bot 2012-03-21 17:55:25 UTC 
Backtrace analysis found this bug to be similar to bug #673001, closing as duplicate.

Bugs which were found to be similar to this bug: bug #649270, bug #652466, bug #657955, bug #667068, bug #668883, bug #673001, bug #702397, bug #702604

This comment is automatically generated.

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