Bug 651306 - [abrt] evolution-data-server-2.32.0-3.fc14: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-data-server-2.32.0-3.fc14: Process /usr/libexec/e-calendar-f...
Keywords:
Status: CLOSED DUPLICATE of bug 649198
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7e353025763113808c968b6bfdc...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-09 08:32 UTC by William Murray
Modified: 2010-11-09 12:50 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-09 12:50:09 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (16.00 KB, text/plain)
2010-11-09 08:32 UTC, William Murray 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.