Bug 587820 - [abrt] crash in cheese-2.28.1-2.fc12: Process /usr/bin/cheese was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in cheese-2.28.1-2.fc12: Process /usr/bin/cheese was killed by s...
Status: CLOSED DUPLICATE of bug 554755
Alias: None
Product: Fedora
Classification: Fedora
Component: cheese   
(Show other bugs)
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:12881cb862249d0f062fd0cc27b...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-30 23:37 UTC by Jeffrey S Austin
Modified: 2010-05-25 10:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 10:20:08 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 (20.27 KB, text/plain)
2010-04-30 23:37 UTC, Jeffrey S Austin 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Jeffrey S Austin 2010-04-30 23:37:39 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: cheese
component: cheese
executable: /usr/bin/cheese
global_uuid: 12881cb862249d0f062fd0cc27b45a31344b82ee
kernel: 2.6.32.11-99.fc12.x86_64
package: cheese-2.28.1-2.fc12
rating: 3
reason: Process /usr/bin/cheese was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Jeffrey S Austin 2010-04-30 23:37:41 UTC 
Created attachment 410614 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 10:20:08 UTC 

*** This bug has been marked as a duplicate of bug 554755 ***
Comment 3 Karel Klíč 2010-05-25 10:20:08 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 #554755.

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