Description of problem: Using Evolution EWS to check corporate 2010 exchange e-mail. While refreshing the folders it hangs. Periodically it crashes. Version-Release number of selected component: evolution-data-server-3.19.3-1.fc24 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory-subprocess --factory ews --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx2606x5 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/2606/5 crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/libexec/evolution-addressbook-factory-subprocess global_pid: 18610 kernel: 4.4.0-0.rc5.git1.1.fc24.x86_64 runlevel: N 5 type: CCpp uid: 10949 Truncated backtrace: Thread no. 1 (8 frames) #0 g_type_check_instance_is_fundamentally_a at gtype.c:4031 #2 soup_socket_properties_unref at soup-socket-properties.c:60 #3 soup_connection_finalize at soup-connection.c:72 #5 soup_session_cleanup_connections at soup-session.c:1374 #6 async_run_queue at soup-session.c:2079 #7 idle_run_queue at soup-session.c:2129 #12 e_ews_soup_thread at e-ews-connection.c:1732 #13 g_thread_proxy at gthread.c:780
Created attachment 1108836 [details] File: backtrace
Created attachment 1108837 [details] File: cgroup
Created attachment 1108838 [details] File: core_backtrace
Created attachment 1108839 [details] File: dso_list
Created attachment 1108840 [details] File: environ
Created attachment 1108841 [details] File: exploitable
Created attachment 1108842 [details] File: limits
Created attachment 1108843 [details] File: maps
Created attachment 1108844 [details] File: mountinfo
Created attachment 1108845 [details] File: namespaces
Created attachment 1108846 [details] File: open_fds
Created attachment 1108847 [details] File: proc_pid_status
Created attachment 1108848 [details] File: var_log_messages
Thanks for a bug report. Does the evolution-ews cause the evolution crash after certain steps for you, please? It can have some coincidence, or require particular data state, used settings and so on. This current crash made the address book backend crash for some reason. If the evolution freezes for a short time, then it can be due to the address book factory crash. I guess. Does also the evolution itself crash? It would be great if you could try to find some steps for the reproducer, then we could debug things further.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.
Since this has been closed for some time I am adding this comment to clear the flag. Keep up the good work. [gsimmons@localhost ~]$ cat /etc/fedora-release Fedora release 32 (Rawhide)