Bug 705028

Summary: [abrt] rhythmbox-0.13.3-1.fc14: g_object_unref: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Petr Kočandrle <pkocandr>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: aban09, bnocera, christermadsen, deadasalways, jonh.wendell, mysteremetal, vishal8492
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8966ffcfe46663e3aa3265b49f5b575495a36077
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 12:34:59 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 Petr Kočandrle 2011-05-16 12:52:32 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 72274 bytes
cmdline: rhythmbox
comment: I had no time to click on anything, it crashed immediately. My collection is not on a hdd in my computer but on a network drive mounted by autofs through nfs protocol, so maybe it has something to do with the crash.
component: rhythmbox
Attached file: coredump, 225591296 bytes
crash_function: g_object_unref
executable: /usr/bin/rhythmbox
kernel: 2.6.35.13-91.fc14.x86_64
package: rhythmbox-0.13.3-1.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1305549339
uid: 500

How to reproduce
-----
1. I've started the app
2. Main window appeared
3. It crashed

Comment 1 Petr Kočandrle 2011-05-16 12:52:35 UTC
Created attachment 499143 [details]
File: backtrace

Comment 2 Petr Kočandrle 2011-06-30 21:10:02 UTC
Package: rhythmbox-2.90.1-10.git20110502.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
I just tryed to run rhythmbox and it crashed during startup. The second try was successful.

Comment 3 Jonh Wendell 2011-07-08 13:06:55 UTC
Package: rhythmbox-2.90.1-10.git20110502.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
Just scrolled down the list of songs

Comment 4 Christer 2011-08-08 19:53:20 UTC
Package: rhythmbox-2.90.1-10.git20110502.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
Double clicked on a radio station, and before it even started playing, Rhythmbox crashed...

Comment 5 Jose Edgar 2011-09-01 20:31:33 UTC
Package: rhythmbox-2.90.1-10.git20110502.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
I just open the application and it crash. I think that the problem is in the autologin of last.fm, but i am not sure.

Comment 6 abrt-bot 2012-03-21 17:45:53 UTC
*** Bug 680631 has been marked as a duplicate of this bug. ***

Comment 7 abrt-bot 2012-03-21 17:46:04 UTC
*** Bug 682411 has been marked as a duplicate of this bug. ***

Comment 8 abrt-bot 2012-03-21 17:46:15 UTC
*** Bug 667612 has been marked as a duplicate of this bug. ***

Comment 9 Fedora End Of Life 2012-08-16 12:35:05 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping