Bug 590270 - [abrt] crash in rhythmbox-0.12.6-5.fc12: raise: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
[abrt] crash in rhythmbox-0.12.6-5.fc12: raise: Process /usr/bin/rhythmbox wa...
Status: CLOSED DUPLICATE of bug 538375
Product: Fedora
Classification: Fedora
Component: rhythmbox (Show other bugs)
12
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
abrt_hash:4aaaaa778859c6b4ca7207ec937...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-08 09:29 EDT by Christopher Beland
Modified: 2010-05-25 05:45 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 05:45:26 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 (25.23 KB, text/plain)
2010-05-08 09:29 EDT, Christopher Beland
no flags Details

  None (edit)
Description Christopher Beland 2010-05-08 09:29:12 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: rhythmbox
comment: Was downloading multiple podcasts simultaneously.
component: rhythmbox
crash_function: raise
executable: /usr/bin/rhythmbox
global_uuid: 4aaaaa778859c6b4ca7207ec937f0f2b57f0ffca
kernel: 2.6.32.12-115.fc12.i686
package: rhythmbox-0.12.6-5.fc12
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 Christopher Beland 2010-05-08 09:29:14 EDT
Created attachment 412530 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 05:45:26 EDT

*** This bug has been marked as a duplicate of bug 538375 ***
Comment 3 Karel Klíč 2010-05-25 05:45:26 EDT
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 #538375.

Sorry for the inconvenience.

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