Bug 590959

Summary: [abrt] crash in evolution-data-server-2.28.3-2.fc12: malloc_consolidate: Process /usr/libexec/evolution-data-server-2.28 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: cnsturgeon2000
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:d07bbe74f45cd0b952d0d51469126dbafe072ecc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-25 09:59:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: backtrace none

Description cnsturgeon2000 2010-05-11 04:53:40 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/evolution-data-server-2.28 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_InterfaceCheck --oaf-ior-fd=36
comment: Tried to double click/single click on the email address on the details of a message in Gmail window
component: evolution-data-server
crash_function: malloc_consolidate
executable: /usr/libexec/evolution-data-server-2.28
global_uuid: d07bbe74f45cd0b952d0d51469126dbafe072ecc
package: evolution-data-server-2.28.3-2.fc12
rating: 4
reason: Process /usr/libexec/evolution-data-server-2.28 was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1. Starting a gmail window with Firefox
2. Click the email address on the details of an email message

Comment 1 cnsturgeon2000 2010-05-11 04:53:43 UTC
Created attachment 413040 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 09:59:05 UTC

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

Comment 3 Karel Klíč 2010-05-25 09:59:05 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 #548005.

Sorry for the inconvenience.