Description of problem: Faf server recevied number of crash reports for this package. Problem URL: https://retrace.fedoraproject.org/faf/problems/bthash/4944176b670a24ff9b08f0227d1ff61bf6f32dab Version-Release number of selected component: evolution-3.6.2-3.fc18.x86_64 Additional info: first occurence: 2013-01-15 09:06 UTC reports count: 39 executable: /usr/bin/evolution Truncated backtrace: # Function Path Source 0 __strlen_sse2_pminub /lib64/libc.so.6 ../sysdeps/x86_64/multiarch/strlen-sse2-pminub.S:38 1 camel_imap_store_summary_path_to_full /usr/lib64/evolution-data-server/camel-providers/libcamelimap.so /camel-imap-store-summary.c:178 2 imap_command_strdup_vprintf /usr/lib64/evolution-data-server/camel-providers/libcamelimap.so /camel-imap-command.c:907 3 imap_command_strdup_printf /usr/lib64/evolution-data-server/camel-providers/libcamelimap.so /camel-imap-command.c:1012 4 camel_imap_command /usr/lib64/evolution-data-server/camel-providers/libcamelimap.so /camel-imap-command.c:113 5 imap_command_start /usr/lib64/evolution-data-server/camel-providers/libcamelimap.so /camel-imap-command.c:219 6 camel_imap_command /usr/lib64/evolution-data-server/camel-providers/libcamelimap.so /camel-imap-command.c:116 7 imap_synchronize_sync /usr/lib64/evolution-data-server/camel-providers/libcamelimap.so /camel-imap-folder.c:1800 8 camel_store_noop_sync /usr/lib64/libcamel-1.2.so.40 /usr/src/debug/evolution-data-server-3.6.2/camel/camel-store.c:3108 9 mail_msg_proxy /usr/lib64/evolution/3.6/libemail-utils.so /mail-mt.c:423 10 g_thread_pool_thread_proxy /usr/lib64/libglib-2.0.so.0 /usr/src/debug/glib-2.34.2/glib/gthreadpool.c:310 11 g_thread_proxy /usr/lib64/libglib-2.0.so.0 /usr/src/debug/glib-2.34.2/glib/gthread.c:797 12 start_thread /lib64/libpthread.so.0 /usr/src/debug/glibc-2.16-75f0d304/nptl/pthread_create.c:308 13 clone /lib64/libc.so.6 ../sysdeps/unix/sysv/linux/x86_64/clone.S:116 This ticket was created automatically. If this report is malformed or not helpful please let us know on crash-catcher.org so we can improve it.
As far as this was filled already as a standard bug report it's a just a waste of all involved time and a plain duplicate. I'm not going to search for exact duplicate number, because there are better things to do.