Bug 587683 - [abrt] crash in rhythmbox-0.12.6-5.fc12: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in rhythmbox-0.12.6-5.fc12: Process /usr/bin/rhythmbox was kille...
Status: CLOSED DUPLICATE of bug 574375
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox   
(Show other bugs)
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:45321d101bdf5f325a89c62abf1...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-30 14:54 UTC by Paolo Niccolò Giubelli
Modified: 2010-05-25 08:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 08:37:18 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 (74.08 KB, text/plain)
2010-04-30 14:54 UTC, Paolo Niccolò Giubelli
no flags Details

Description Paolo Niccolò Giubelli 2010-04-30 14:54:37 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: rhythmbox
component: rhythmbox
executable: /usr/bin/rhythmbox
global_uuid: 45321d101bdf5f325a89c62abf1ffb523681d823
kernel: 2.6.32.11-99.fc12.i686.PAE
package: rhythmbox-0.12.6-5.fc12
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 Paolo Niccolò Giubelli 2010-04-30 14:54:41 UTC
Created attachment 410508 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 08:37:18 UTC

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

Comment 3 Karel Klíč 2010-05-25 08:37:18 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 #574375.

Sorry for the inconvenience.


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