Version-Release number of selected component: evolution-3.13.7-1.fc22 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: evolution jobcroc?subject=Python-%D1%80%D0%B0%D0%B7%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D1%87%D0%B8%D0%BA crash_function: magazine_chain_pop_head executable: /usr/bin/evolution kernel: 3.17.1-302.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:1808 #7 g_object_new_valist at gobject.c:2034 #9 g_network_address_parse_uri at gnetworkaddress.c:757 #10 g_proxy_address_enumerator_constructed at gproxyaddressenumerator.c:581 Potential duplicate: bug 701604
Created attachment 952621 [details] File: backtrace
Created attachment 952622 [details] File: cgroup
Created attachment 952623 [details] File: core_backtrace
Created attachment 952624 [details] File: dso_list
Created attachment 952625 [details] File: environ
Created attachment 952626 [details] File: exploitable
Created attachment 952627 [details] File: limits
Created attachment 952628 [details] File: maps
Created attachment 952629 [details] File: open_fds
Created attachment 952630 [details] File: proc_pid_status
Created attachment 952631 [details] File: var_log_messages
Thanks for a bug report. I see from the backtrace that the crash is most likely caused by a memory corruption (for example some code could access already freed memory), when evolution was resolving a server address and sending a message. Do you have any steps for a reproducer, please? Also, do you use any proxy server for connection, either system-wide configured, or configured inside Evolution, at Edit->Preferences->Network Preferences? I'd guess from the above backtrace and information that you: a) clicked some "mailto:" link to send a message b) a message composer opened, where you filled the message body and such c) sent the message, when the crash happened I also guess that the evolution was not running before doing this.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Can't reproduce anymore.