Bug 652873

Summary: [abrt] rhythmbox-0.13.1-2.fc14: decode_slice_header: Process /usr/libexec/rhythmbox-metadata was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: beat <beat.gerber>
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
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:7c5fceef53ad8505c97c1b479414c8fb5f689a8e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 17:48:30 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 beat 2010-11-13 06:13:03 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/rhythmbox-metadata unix:tmpdir=/tmp
comment:  I don't know how to reproduce it, but this error is comming up often
component: rhythmbox
crash_function: decode_slice_header
executable: /usr/libexec/rhythmbox-metadata
kernel: 2.6.35.6-48.fc14.x86_64
package: rhythmbox-0.13.1-2.fc14
rating: 4
reason: Process /usr/libexec/rhythmbox-metadata was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289627836
uid: 503

How to reproduce
-----
1. finishing downloading a podcast
2. listen to magnatune
3.
Comment 1 beat 2010-11-13 06:13:06 UTC 
Created attachment 460199 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 17:48:30 UTC 
Backtrace analysis found this bug to be similar to bug #719086, closing as duplicate. This bug seems to belong to component gstreamer.

Bugs which were found to be similar to this bug: 
  rhythmbox: bug #719086, bug #730623, bug #739351
  rygel: bug #662528
  totem: bug #736073

This comment is automatically generated.

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