Bug 613788 - [abrt] crash in rhythmbox-0.12.8-4.fc13: raise: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
[abrt] crash in rhythmbox-0.12.8-4.fc13: raise: Process /usr/bin/rhythmbox wa...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: rhythmbox (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
abrt_hash:c651bccfe076c7384cbcc8876de...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-12 16:04 EDT by Nathanael Noblet
Modified: 2010-07-12 21:59 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-12 21:59:54 EDT
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 (63.10 KB, text/plain)
2010-07-12 16:04 EDT, Nathanael Noblet
no flags Details

  None (edit)
Description Nathanael Noblet 2010-07-12 16:04:02 EDT
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 16:04:04 EDT
Created attachment 431258 [details]
File: backtrace
Comment 2 Nathanael Noblet 2010-07-12 21:59:54 EDT
I ended up having major hardware issues later in the day. I'm 95% positive this was an early warning of that hardware issue

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