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
Created attachment 676456 [details] File: core_backtrace
Created attachment 676457 [details] File: environ
Created attachment 676458 [details] File: limits
Created attachment 676459 [details] File: backtrace
Created attachment 676460 [details] File: cgroup
Created attachment 676461 [details] File: gconf_subtree
Created attachment 676462 [details] File: smolt_data
Created attachment 676463 [details] File: executable
Created attachment 676464 [details] File: maps
Created attachment 676465 [details] File: dso_list
Created attachment 676466 [details] File: build_ids
Created attachment 676467 [details] File: proc_pid_status
Created attachment 676468 [details] File: var_log_messages
Created attachment 676469 [details] File: open_fds
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 ***