Version-Release number of selected component: evolution-3.12.7-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: evolution crash_function: magazine_chain_pop_head executable: /usr/bin/evolution kernel: 3.17.1-304.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:539 #1 thread_memory_magazine1_alloc at gslice.c:842 #2 g_slice_alloc at gslice.c:998 #3 g_slist_prepend at gslist.c:254 #4 g_object_notify_queue_add at gobject.c:305 #5 object_set_property at gobject.c:1424 #6 g_object_new_internal at gobject.c:1828 #7 g_object_new_valist at gobject.c:2034 #9 e_soap_message_new_from_uri at e-soap-message.c:390 #10 e_soap_message_new at e-soap-message.c:340 Potential duplicate: bug 701604
Created attachment 951387 [details] File: backtrace
Created attachment 951388 [details] File: cgroup
Created attachment 951389 [details] File: core_backtrace
Created attachment 951390 [details] File: dso_list
Created attachment 951391 [details] File: environ
Created attachment 951392 [details] File: exploitable
Created attachment 951393 [details] File: limits
Created attachment 951394 [details] File: maps
Created attachment 951395 [details] File: open_fds
Created attachment 951396 [details] File: proc_pid_status
Created attachment 951397 [details] File: var_log_messages
Thanks for a bug report. I guess this is related to your bug #1158055. Did it happen after a similar circumstances (after sending a message through your EWS account)?
Well, yes it's possible, cause I'm using evo only for EWS :)
Okay. Let's cover this under that other bug report too. *** This bug has been marked as a duplicate of bug 1158055 ***