Bug 589114 - [abrt] crash in grip-1:3.2.0-29.fc12: Process /usr/bin/grip was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in grip-1:3.2.0-29.fc12: Process /usr/bin/grip was killed by sig...
Status: CLOSED DUPLICATE of bug 558381
Alias: None
Product: Fedora
Classification: Fedora
Component: grip   
(Show other bugs)
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adrian Reber
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:619379810514881aaaf3bac5985...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-05 12:30 UTC by conorarmstrong
Modified: 2010-05-25 09:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 09:53:48 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 (42.86 KB, text/plain)
2010-05-05 12:30 UTC, conorarmstrong 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description conorarmstrong 2010-05-05 12:30:08 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: grip
component: grip
executable: /usr/bin/grip
global_uuid: 619379810514881aaaf3bac59852b1d21328da9a
kernel: 2.6.32.11-99.fc12.x86_64
package: grip-1:3.2.0-29.fc12
rating: 4
reason: Process /usr/bin/grip was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.1.rip a cd - intermittant
2.
3.
Comment 1 conorarmstrong 2010-05-05 12:30:11 UTC 
Created attachment 411575 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:53:48 UTC 

*** This bug has been marked as a duplicate of bug 558381 ***
Comment 3 Karel Klíč 2010-05-25 09:53:48 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 #558381.

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