Version-Release number of selected component: evolution-3.10.4-2.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 3 cmdline: evolution executable: /usr/bin/evolution kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 ?? #7 gtk_dialog_run at gtkdialog.c:1075 #8 mailto_handler_prompt at evolution-mailto-handler.c:171 #9 mailto_handler_check at evolution-mailto-handler.c:204 #14 e_shell_event at e-shell.c:1714 Potential duplicate: bug 866207
Created attachment 879450 [details] File: backtrace
Created attachment 879451 [details] File: cgroup
Created attachment 879452 [details] File: core_backtrace
Created attachment 879453 [details] File: dso_list
Created attachment 879454 [details] File: environ
Created attachment 879455 [details] File: exploitable
Created attachment 879456 [details] File: limits
Created attachment 879457 [details] File: maps
Created attachment 879458 [details] File: open_fds
Created attachment 879459 [details] File: proc_pid_status
Created attachment 879460 [details] File: var_log_messages
Thanks for a bug report. I think this happened due to a memory corruption (like if some part of the code writes to an already freed memory, or any other kind of a similar issue), which exhibits this way. I see from the logs that you updated evolution packages just before the crash. Maybe that's the reason, part of the libraries were "remembered" by the system from the previous version and other part was used from the new version. Does it help, if you restart the whole machine, which will make sure that only the updated binaries are used?
After restart It seems to be fine.