Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 g_io_stream_get_input_stream at giostream.c:231
#1 new_iostate at soup-message-io.c:1185
#2 soup_message_io_client at soup-message-io.c:1215
#3 soup_message_send_request at soup-message-client-io.c:161
#4 soup_connection_send_request at soup-connection.c:708
#5 soup_session_send_queue_item at soup-session.c:1326
#6 soup_session_process_queue_item at soup-session.c:1987
#7 soup_session_real_send_message at soup-session.c:2218
#8 e_ews_notification_unsubscribe_folder_sync at /usr/src/debug/evolution-ews-3.24.4/src/server/e-ews-notification.c:485
#9 e_ews_notification_get_events_thread at /usr/src/debug/evolution-ews-3.24.4/src/server/e-ews-notification.c:882
Created attachment 1307809 [details]
Created attachment 1307810 [details]
Created attachment 1307811 [details]
Created attachment 1307812 [details]
Created attachment 1307813 [details]
Created attachment 1307814 [details]
Created attachment 1307815 [details]
Created attachment 1307816 [details]
Created attachment 1307817 [details]
Created attachment 1307818 [details]
Created attachment 1307819 [details]
Created attachment 1307820 [details]
Thanks for a bug report. I see from the backtrace that the crash happened when evolution-ews tried to unsubscribe an event listener, which is used to receive notifications about changes on the server. There had been also something going on in painting, I guess one of the accounts had been connecting or something, but the other threads do not look like that. The var_log_messages file shows runtime warnings related to libsoup, thus most likely also connected to evolution-ews.
I'm not sure how to reproduce this. Did it happen for the first time for you, or you see this regularly? Eventually after any particular action? It can be even a connection state change, like when switching networks or anything like that.
I've been using Evolution with Exchange for months on that system, back when Fedora 26 was in Beta. There were no changes to Evolution configuration in the days before the crash. I don't remember Evolution crashing on the system before. That was a one-off event. I went to lunch while Evolution was open. When I came back, the system was locked (which is normal), and there was a message that Evolution had crashed. I'm using the default GNOME desktop on X11 (XDG_SESSION_TYPE=x11).
I have no idea how to reproduce the crash, but I'll keep Evolution running while going to lunch :)
Thanks for the update. I'll keep the bug open for the time being, though I understand this could be just some corner-case issue, thus very hard to reproduce.
*** Bug 1541154 has been marked as a duplicate of this bug. ***
*** Bug 1559461 has been marked as a duplicate of this bug. ***
*** Bug 1566779 has been marked as a duplicate of this bug. ***
*** Bug 1574381 has been marked as a duplicate of this bug. ***
I tried to reproduce this by going from online to offline, as suggested in the last duplicate filled for Fedora 28, but no luck. Neither when running under valgrind, which can catch certain memory issues or at least log about them. I'm afraid it requires some other consequences. What I know about is that libsoup has some issues, but it might not be necessary directly related:
*** Bug 1545719 has been marked as a duplicate of this bug. ***
*** Bug 1600724 has been marked as a duplicate of this bug. ***
*** Bug 1674138 has been marked as a duplicate of this bug. ***
*** Bug 1696696 has been marked as a duplicate of this bug. ***
*** Bug 1738413 has been marked as a duplicate of this bug. ***
*** Bug 1748320 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.
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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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
Thank you for reporting this bug and we are sorry it could not be fixed.