Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 551799

Summary: [abrt] crash detected in empathy-2.28.2-1.fc12
Product: [Fedora] Fedora Reporter: Michael <mdhensley>
Component: empathyAssignee: Peter Gordon <peter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: bdpepple, kklic, lpoetter, peter
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:b1827631e894bc880f0af3c09f8f8b1a8a65c4a6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-02 16:26:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Michael 2010-01-02 05:32:32 UTC 
abrt 1.0.0 detected a crash.

Attached file: backtrace
cmdline: empathy
component: empathy
executable: /usr/bin/empathy
kernel: 2.6.31.9-174.fc12.x86_64
package: empathy-2.28.2-1.fc12
rating: 3
reason: Process was terminated by signal 11
Comment 1 Michael 2010-01-02 05:32:33 UTC 
Created attachment 381247 [details]
File: backtrace
Comment 2 Brian Pepple 2010-01-02 05:38:12 UTC 

*** This bug has been marked as a duplicate of bug 532307 ***
Comment 3 Lennart Poettering 2010-01-11 22:48:00 UTC 
Not PA either. Man this gets annoying.
Comment 4 Karel Klíč 2010-03-02 16:26:40 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 #552064.

Sorry for the inconvenience.

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