Bug 894113

Summary: [abrt] evolution-3.4.4-2.fc17: __alloc_dir: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Shuresh Williams <stressfreechozeme>
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: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:fa79442169fb004501fed1d184995924e375710a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-11 07:39:02 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: maps
none
File: dso_list
none
File: build_ids
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Shuresh Williams 2013-01-10 18:29:13 UTC 
Description of problem:
Deleted mails the attempted to empty the trash I got and I/O error and the trash did not empty, nor were they remove from POP 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: __alloc_dir
kernel:         3.6.11-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (9 frames)
: #3 __alloc_dir at ../sysdeps/unix/opendir.c:200
: #4 maildir_summary_check at camel-maildir-summary.c:562
: #5 maildir_summary_sync at camel-maildir-summary.c:743
: #6 local_folder_synchronize_sync at camel-local-folder.c:429
: #7 camel_folder_synchronize_sync at camel-folder.c:4033
: #8 vee_folder_synchronize_sync at camel-vee-folder.c:1425
: #9 camel_folder_expunge_sync at camel-folder.c:3324
: #10 mail_msg_proxy at mail-mt.c:423
: #12 g_thread_proxy at gthread.c:801
Comment 1 Shuresh Williams 2013-01-10 18:29:16 UTC 
Created attachment 676456 [details]
File: core_backtrace
Comment 2 Shuresh Williams 2013-01-10 18:29:17 UTC 
Created attachment 676457 [details]
File: environ
Comment 3 Shuresh Williams 2013-01-10 18:29:19 UTC 
Created attachment 676458 [details]
File: limits
Comment 4 Shuresh Williams 2013-01-10 18:29:21 UTC 
Created attachment 676459 [details]
File: backtrace
Comment 5 Shuresh Williams 2013-01-10 18:29:23 UTC 
Created attachment 676460 [details]
File: cgroup
Comment 6 Shuresh Williams 2013-01-10 18:29:24 UTC 
Created attachment 676461 [details]
File: gconf_subtree
Comment 7 Shuresh Williams 2013-01-10 18:29:26 UTC 
Created attachment 676462 [details]
File: smolt_data
Comment 8 Shuresh Williams 2013-01-10 18:29:28 UTC 
Created attachment 676463 [details]
File: executable
Comment 9 Shuresh Williams 2013-01-10 18:29:29 UTC 
Created attachment 676464 [details]
File: maps
Comment 10 Shuresh Williams 2013-01-10 18:29:32 UTC 
Created attachment 676465 [details]
File: dso_list
Comment 11 Shuresh Williams 2013-01-10 18:29:33 UTC 
Created attachment 676466 [details]
File: build_ids
Comment 12 Shuresh Williams 2013-01-10 18:29:35 UTC 
Created attachment 676467 [details]
File: proc_pid_status
Comment 13 Shuresh Williams 2013-01-10 18:29:37 UTC 
Created attachment 676468 [details]
File: var_log_messages
Comment 14 Shuresh Williams 2013-01-10 18:29:38 UTC 
Created attachment 676469 [details]
File: open_fds
Comment 15 Milan Crha 2013-01-11 07:39:02 UTC 
Thanks for a bug report, I see this is a memory corruption bug, similar to yours bug #893290, and the corresponding upstream bug I chose for the bug #893290 also mentions similar backtrace like that yours here, thus I'm marking this as a duplicate of it. I'd suggest to try to update to the to-be-released-soon Fedora 18, with Evolution 3.6.x, which might be better on this now.

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