Bug 613788

Summary: [abrt] crash in rhythmbox-0.12.8-4.fc13: raise: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Nathanael Noblet <nathanael>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:c651bccfe076c7384cbcc8876de08260045546cf
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-13 01:59:54 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 Nathanael Noblet 2010-07-12 20:04:02 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: rhythmbox
comment: I didn't do anything it was just running in the background. I left for a bit and it had crashed when I came back
component: rhythmbox
crash_function: raise
executable: /usr/bin/rhythmbox
global_uuid: c651bccfe076c7384cbcc8876de08260045546cf
kernel: 2.6.33.6-147.fc13.x86_64
package: rhythmbox-0.12.8-4.fc13
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Left it running
2.
3.
Comment 1 Nathanael Noblet 2010-07-12 20:04:04 UTC 
Created attachment 431258 [details]
File: backtrace
Comment 2 Nathanael Noblet 2010-07-13 01:59:54 UTC 
I ended up having major hardware issues later in the day. I'm 95% positive this was an early warning of that hardware issue