Version-Release number of selected component: evolution-3.16.5-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: evolution crash_function: imapx_continuation executable: /usr/bin/evolution global_pid: 8835 kernel: 4.1.6-201.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 imapx_continuation at camel-imapx-server.c:3192 #1 imapx_step at camel-imapx-server.c:3496 #2 imapx_ready_to_read at camel-imapx-server.c:7813 #7 imapx_parser_thread at camel-imapx-server.c:7931 #8 g_thread_proxy at gthread.c:764
Created attachment 1077121 [details] File: backtrace
Created attachment 1077124 [details] File: cgroup
Created attachment 1077127 [details] File: core_backtrace
Created attachment 1077130 [details] File: dso_list
Created attachment 1077131 [details] File: environ
Created attachment 1077132 [details] File: limits
Created attachment 1077133 [details] File: maps
Created attachment 1077134 [details] File: mountinfo
Created attachment 1077135 [details] File: namespaces
Created attachment 1077136 [details] File: open_fds
Created attachment 1077137 [details] File: proc_pid_status
Created attachment 1077138 [details] File: var_log_messages
Thanks for a bug report. One part of the backtrace is gone in the current stable version of the evolution-data-server, 3.18.0, thus I'd suggest to update to Fedora 23 once it'll be released, with which you get also the 3.18.0 version. It doesn't mean that the issue as such is fixed there, it's mainly the backtrace which will be different. Can you reproduce the crash reliably, with certain steps, please?
No I cannot reproduce the crash reliably. So I closed this bug. If the crash happens again, I will update this bug report.