Bug 710255 - [abrt] evolution-2.32.2-1.fc14: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.2-1.fc14: Process /usr/bin/evolution was killed by sign...
Keywords:
Status: CLOSED DUPLICATE of bug 661854
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:edc30fef0fbbc1b63cbf4b3c1e5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-02 20:06 UTC by Jeremy Mordkoff
Modified: 2011-06-03 06:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-03 06:17:42 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (65.16 KB, text/plain)
2011-06-02 20:06 UTC, Jeremy Mordkoff
no flags Details

Description Jeremy Mordkoff 2011-06-02 20:06:06 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 66723 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 136785920 bytes
crash_function: camel_exchange_folder_construct
executable: /usr/bin/evolution
kernel: 2.6.35.13-91.fc14.x86_64
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1307044361
uid: 509

How to reproduce
-----
1. system crashed when I tried to write a DVD
2. when it came back up, I logged in but evolution crashes on startup every time  -- need help
3.  evolution is connected to my exchange 2003 server

Comment 1 Jeremy Mordkoff 2011-06-02 20:06:08 UTC
Created attachment 502629 [details]
File: backtrace

Comment 2 Milan Crha 2011-06-03 06:17:42 UTC
Thanks for a bug report. I guess your folder.db file for the exchange account is corrupted after the crash, thus I suggest to remove whole local cache and let recreate it the next start. It's OK, because everything is stored on the server. The only disadvantage is that the remove messages will be redownloaded again.
You can remove the local cache like this:
a) close evolution
b) make sure also e-addressbook-factory, e-calendar-factory and
   evolution-alarm-notify processes are not running
c) move away folders:
   ~/.local/share/evolution/exchange
   ~/.local/share/evolution/mail/exchange
d) run evolution

Rather move those folders away, than delete them, in case something will break even more and you'll need to revert back.

I found a similar bug already filled, thus I'm marking this one as its duplicate. Feel free to ask here if you'll have something unclear.

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


Note You need to log in before you can comment on or make changes to this bug.