Bug 586041 - [abrt] crash in rhythmbox-0.12.8-3.fc13: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in rhythmbox-0.12.8-3.fc13: Process /usr/bin/rhythmbox was kille...
Status: CLOSED DUPLICATE of bug 560667
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox   
(Show other bugs)
Version: 13
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:866001d430841d934b38f1fd679...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-26 17:09 UTC by ssbenichou
Modified: 2010-05-25 09:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 09:17:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (72.98 KB, text/plain)
2010-04-26 17:09 UTC, ssbenichou 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description ssbenichou 2010-04-26 17:09:03 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: rhythmbox
component: rhythmbox
executable: /usr/bin/rhythmbox
global_uuid: 866001d430841d934b38f1fd679bbe90c9b20068
kernel: 2.6.33.2-57.fc13.i686
package: rhythmbox-0.12.8-3.fc13
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Play Flac file
2.
3.
Comment 1 ssbenichou 2010-04-26 17:09:08 UTC 
Created attachment 409235 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:17:55 UTC 

*** This bug has been marked as a duplicate of bug 560667 ***
Comment 3 Karel Klíč 2010-05-25 09:17:55 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #560667.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.