Bug 651306

Summary: [abrt] evolution-data-server-2.32.0-3.fc14: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: William Murray <w.j.murray>
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: 14CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:7e353025763113808c968b6bfdcbd4e30f9aee1d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 12:50:09 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 William Murray 2010-11-09 08:32:56 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/e-calendar-factory
comment: This was done on a FC14 VM to ensure no egacy'from my old installation. The same things happens on bare metal.
component: evolution-data-server
executable: /usr/libexec/e-calendar-factory
kernel: 2.6.35.6-48.fc14.x86_64
package: evolution-data-server-2.32.0-3.fc14
reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289291276
uid: 500

How to reproduce
-----
1.
2.
3.
Configure evolution with exchange 2003
start evolution
Comment 1 William Murray 2010-11-09 08:32:59 UTC 
Created attachment 459032 [details]
File: backtrace
Comment 2 Milan Crha 2010-11-09 12:50:09 UTC 
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate.

You can workaround this by invoking a command:
 $ mkdir ~/.cache/evolution/calendar
before running evolution.

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