Bug 591618

Summary: [abrt] crash in evolution-2.30.1-3.fc13: check_server_for_object: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Chad Feller <cfeller>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:cd42f433e03f5ab6711999a848cbf20478e15768
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-13 08:19:58 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 Chad Feller 2010-05-12 17:36:10 UTC 
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: check_server_for_object
executable: /usr/bin/evolution
global_uuid: cd42f433e03f5ab6711999a848cbf20478e15768
kernel: 2.6.33.3-85.fc13.x86_64
package: evolution-2.30.1-3.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

comment
-----
this ABRT crash was produced by the circumstances in bug #587726.  
The difference is that when I opened evolution, the message that it opened on was a meeting invite, which caused a crash that ABRT picked up.

How to reproduce
-----
1. (see comment)
Comment 1 Chad Feller 2010-05-12 17:36:12 UTC 
Created attachment 413497 [details]
File: backtrace
Comment 2 Chad Feller 2010-05-12 18:27:58 UTC 
Package: evolution-2.30.1-3.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. (see comment)
2.
3.


Comment
-----
This was produced by the exact circumstances as bug# 587726
Comment 3 Milan Crha 2010-05-13 08:19:58 UTC 
Thanks for a bug report. Seeing the attached backtrace it exactly the same crash as in the bug you mentioned. I'm closing this as a duplicate.

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