Bug 693378

Summary: [abrt] evolution-2.32.2-1.fc14: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Larry O'Leary <loleary>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:3cea3d5b55f4b6a7e2c5e170f52d96471e614e98
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-05 06:09:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Larry O'Leary 2011-04-04 13:48:55 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 89824 bytes
cmdline: evolution
comment: As reported before, this appears to occur after a fresh startup or after Evolution has been closed for a while. In other words, if I lauch Evolution a second time, it seems to open just fine. If I close it and then relaunch it within a minutes or so, again, it opens just fine. But if I close it and leave it closed for a couple hours, relaunch results in the crash as well.
component: evolution
Attached file: coredump, 219508736 bytes
crash_function: camel_folder_search_set_folder
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.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: 1301924268
uid: 500

How to reproduce
-----
1. Launch Evolution
Comment 1 Larry O'Leary 2011-04-04 13:48:58 UTC 
Created attachment 489775 [details]
File: backtrace
Comment 2 Milan Crha 2011-04-05 06:09:47 UTC 
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate.

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