Bug 661191

Summary: [abrt] rhythmbox-0.13.1-2.fc14: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Bob Arendt <rda>
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, brendan.jones.it, e.liger
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:bd7da33ea629b5a60b1fc4992b951085a0b44c96
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-26 00:20:46 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 Bob Arendt 2010-12-08 04:14:15 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: rhythmbox
component: rhythmbox
crash_function: rb_player_gst_find_element_with_property
executable: /usr/bin/rhythmbox
kernel: 2.6.35.6-48.fc14.x86_64
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: 1291778417
uid: 500

How to reproduce
-----
1. Start rythmbox
2. Select  a song
3. Click play and it crashes
Comment 1 Bob Arendt 2010-12-08 04:14:17 UTC 
Created attachment 467360 [details]
File: backtrace
Comment 2 Eric Liger 2010-12-16 20:25:31 UTC 
Package: rhythmbox-0.13.1-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.lancer une webradio
2.
3.
Comment 3 Bob Arendt 2010-12-20 05:19:38 UTC 
After a fresh F14 install (but old home directory) rhythmbox was attempting to use codecs that no longer existed and threw a signal 11.  It was my configuration error - installing additional codecs and wiping/rebuilding the rhythmbox configs in my home directory fixed it.  But the internal diagnostics could certainly be improved.  My problem was misconfiguration - perhaps this happened to Eric (comment#2) as well?
Comment 4 Brendan Jones 2010-12-26 00:20:46 UTC 

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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