Bug 906380

Summary: [abrt] evolution-3.4.4-2.fc17: data_cache_path: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: schladsb
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:6a7548ca1c5b2842520f84b7ba32e94680ff92b3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-01 08:00:03 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: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: gconf_subtree
none
File: smolt_data
none
File: executable
none
File: xsession_errors
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description schladsb 2013-01-31 14:43:20 UTC 
Description of problem:
I was switching from the inbox to another folder. Note that the inbox and folder I was using are housed on an 2007 exchange server.

Version-Release number of selected component:
evolution-3.4.4-2.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        evolution
crash_function: data_cache_path
kernel:         3.7.3-101.fc17.i686.PAE

truncated backtrace:
:Thread no. 1 (7 frames)
: #0 data_cache_path at camel-data-cache.c:329
: #1 camel_data_cache_remove at camel-data-cache.c:495
: #2 mapi_folder_synchronize_sync at camel-mapi-folder.c:1765
: #3 camel_folder_synchronize_sync at camel-folder.c:4033
: #4 sync_folder_exec at mail-ops.c:1172
: #5 mail_msg_proxy at mail-mt.c:423
: #7 g_thread_proxy at gthread.c:801
Comment 1 schladsb 2013-01-31 14:43:22 UTC 
Created attachment 690942 [details]
File: core_backtrace
Comment 2 schladsb 2013-01-31 14:43:24 UTC 
Created attachment 690943 [details]
File: environ
Comment 3 schladsb 2013-01-31 14:43:26 UTC 
Created attachment 690944 [details]
File: limits
Comment 4 schladsb 2013-01-31 14:43:31 UTC 
Created attachment 690945 [details]
File: backtrace
Comment 5 schladsb 2013-01-31 14:43:32 UTC 
Created attachment 690946 [details]
File: cgroup
Comment 6 schladsb 2013-01-31 14:43:34 UTC 
Created attachment 690947 [details]
File: gconf_subtree
Comment 7 schladsb 2013-01-31 14:43:36 UTC 
Created attachment 690948 [details]
File: smolt_data
Comment 8 schladsb 2013-01-31 14:43:38 UTC 
Created attachment 690949 [details]
File: executable
Comment 9 schladsb 2013-01-31 14:43:39 UTC 
Created attachment 690950 [details]
File: xsession_errors
Comment 10 schladsb 2013-01-31 14:43:41 UTC 
Created attachment 690951 [details]
File: maps
Comment 11 schladsb 2013-01-31 14:43:45 UTC 
Created attachment 690952 [details]
File: dso_list
Comment 12 schladsb 2013-01-31 14:43:47 UTC 
Created attachment 690953 [details]
File: proc_pid_status
Comment 13 schladsb 2013-01-31 14:43:48 UTC 
Created attachment 690954 [details]
File: var_log_messages
Comment 14 schladsb 2013-01-31 14:43:50 UTC 
Created attachment 690955 [details]
File: open_fds
Comment 15 Milan Crha 2013-02-01 08:00:03 UTC 
Thanks for a bug report. I thought I'll suggest to update to more recent version, like 3.6.x in Fedora 18, but looking more closely it seems it's still there, as was reported in bug #903051, which has a similar backtrace. I'm marking this as a duplicate of it.

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