Bug 676989

Summary: [abrt] rhythmbox-0.13.3-1.fc14: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Yann Droneaud <yann>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c588785b0a0203f773215eb4ec7926a7d77f5e2d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 14:29:32 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 Yann Droneaud 2011-02-12 09:57:11 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: rhythmbox '/home/cgalietti/.gvfs/point de montage cdda sur sr0'
component: rhythmbox
executable: /usr/bin/rhythmbox
kernel: 2.6.35.10-74.fc14.x86_64
package: rhythmbox-0.13.3-1.fc14
rating: 3
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1297504212
uid: 501

How to reproduce
-----
1. Importing  a corrupted audio CD.

scsi_read error: sector=0 length=9 retry=1
                 Sense key: 3 ASC: 11 ASCQ: 6
                 Transport error: Medium reading data from medium
                 System error: Erreur d'entrée/sortie
scsi_read error: sector=0 length=4 retry=2
                 Sense key: 3 ASC: 11 ASCQ: 6
                 Transport error: Medium reading data from medium
                 System error: Erreur d'entrée/sortie

2. Removing the audio while trying to encode it.

Comment 1 Yann Droneaud 2011-02-12 09:57:14 UTC
Created attachment 478369 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-21 14:29:32 UTC
Backtrace analysis found this bug to be similar to bug #702009, closing as duplicate.

Bugs which were found to be similar to this bug: bug #571990, bug #702009

This comment is automatically generated.

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