Version-Release number of selected component: evolution-3.16.5-3.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: evolution crash_function: g_inet_socket_address_dispose executable: /usr/bin/evolution global_pid: 2739 kernel: 4.1.10-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 g_inet_socket_address_dispose at ginetsocketaddress.c:72 #3 g_list_foreach at glist.c:1005 #4 g_list_free_full at glist.c:220 #5 g_network_address_address_enumerator_next at gnetworkaddress.c:918 #6 g_proxy_address_enumerator_next at gproxyaddressenumerator.c:210 #7 g_network_monitor_base_can_reach at gnetworkmonitorbase.c:204 #8 camel_network_service_can_reach_sync at camel-network-service.c:932 #9 camel_offline_store_set_online_sync at camel-offline-store.c:194 #10 e_mail_store_go_online_sync at e-mail-store-utils.c:268 #11 mail_folder_cache_note_store_thread at mail-folder-cache.c:1859
Created attachment 1082906 [details] File: backtrace
Created attachment 1082907 [details] File: cgroup
Created attachment 1082908 [details] File: core_backtrace
Created attachment 1082909 [details] File: dso_list
Created attachment 1082910 [details] File: environ
Created attachment 1082911 [details] File: limits
Created attachment 1082912 [details] File: maps
Created attachment 1082913 [details] File: mountinfo
Created attachment 1082914 [details] File: namespaces
Created attachment 1082915 [details] File: open_fds
Created attachment 1082916 [details] File: proc_pid_status
Created attachment 1082917 [details] File: var_log_messages
Thanks for a bug report. I think the crash is related to an upstream bug [1]. I asked there for their opinion. [1] https://bugzilla.gnome.org/show_bug.cgi?id=748996
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.