Description of problem: I was checking my email then I emptied the trash, it did the deletion process. @ 99% of the explunge it evolution crashed. It is configured to delete the emails from POP server when explunge is done but it never works always crashes. 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: strlen kernel: 3.6.11-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (9 frames) : #0 strlen at ../sysdeps/x86_64/strlen.S:43 : #1 camel_pop3_engine_iterate at camel-pop3-engine.c:348 : #3 camel_pop3_store_expunge at camel-pop3-store.c:812 : #4 pop3_folder_synchronize_sync at camel-pop3-folder.c:885 : #5 camel_folder_synchronize_sync at camel-folder.c:4033 : #6 expunge_pop3_stores at mail-ops.c:1494 : #7 expunge_folder_exec at mail-ops.c:1564 : #8 mail_msg_proxy at mail-mt.c:423 : #10 g_thread_proxy at gthread.c:801
Created attachment 675202 [details] File: core_backtrace
Created attachment 675203 [details] File: environ
Created attachment 675204 [details] File: event_log
Created attachment 675205 [details] File: limits
Created attachment 675206 [details] File: backtrace
Created attachment 675207 [details] File: gconf_subtree
Created attachment 675208 [details] File: cgroup
Created attachment 675209 [details] File: smolt_data
Created attachment 675210 [details] File: executable
Created attachment 675211 [details] File: maps
Created attachment 675212 [details] File: dso_list
Created attachment 675213 [details] File: build_ids
Created attachment 675214 [details] File: proc_pid_status
Created attachment 675215 [details] File: var_log_messages
Created attachment 675216 [details] File: open_fds
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions. [1] https://bugzilla.gnome.org/show_bug.cgi?id=667108
*** Bug 894113 has been marked as a duplicate of this bug. ***