Bug 595189 - [abrt] crash in cheese-2.30.1-1.fc13: Process /usr/bin/cheese was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in cheese-2.30.1-1.fc13: Process /usr/bin/cheese was killed by s...
Status: CLOSED DUPLICATE of bug 554093
Alias: None
Product: Fedora
Classification: Fedora
Component: cheese   
(Show other bugs)
Version: 13
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:04eff0eeff05ea9806401b89485...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-23 23:28 UTC by Alejandro_Perez
Modified: 2010-05-25 09:16 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:16:45 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 (85.31 KB, text/plain)
2010-05-23 23:28 UTC, Alejandro_Perez 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Alejandro_Perez 2010-05-23 23:28:32 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: cheese
component: cheese
executable: /usr/bin/cheese
global_uuid: 04eff0eeff05ea9806401b89485eaa835bfba006
kernel: 2.6.33.4-95.fc13.i686.PAE
package: cheese-2.30.1-1.fc13
rating: 3
reason: Process /usr/bin/cheese was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.Started cheese
2.
3.
Comment 1 Alejandro_Perez 2010-05-23 23:28:35 UTC 
Created attachment 416004 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:16:45 UTC 

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

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