Fedora Account System
Red Hat Associate
Red Hat Customer
Version-Release number of selected component: evolution-data-server-3.30.4-1.fc29 Additional info: reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: ews_notification_soup_got_chunk environ: executable: /usr/libexec/evolution-calendar-factory journald_cursor: s=3acb7dfc02bc4a688cc4924a37f0b79d;i=5fe00;b=ffb36028cd954db0836b98019280b804;m=124d95b6c1;t=5812a87a4d1e1;x=4f19998b1c786895 kernel: 4.20.4-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 17 (10 frames) #0 ews_notification_soup_got_chunk at /usr/src/debug/evolution-ews-3.30.3-1.fc29.x86_64/src/server/e-ews-notification.c:698 #1 g_cclosure_marshal_VOID__BOXEDv at gmarshal.c:1950 #2 _g_closure_invoke_va at gclosure.c:873 #5 soup_message_got_chunk at soup-message.c:1134 #6 io_read at soup-message-io.c:774 #7 io_run_until at soup-message-io.c:986 #8 io_run at soup-message-io.c:1057 #9 soup_message_io_client at soup-message-io.c:1237 #10 soup_message_send_request at soup-message-client-io.c:161 #11 soup_connection_send_request at soup-connection.c:718
Created attachment 1527306 [details] File: backtrace
Created attachment 1527307 [details] File: cgroup
Created attachment 1527308 [details] File: core_backtrace
Created attachment 1527309 [details] File: cpuinfo
Created attachment 1527310 [details] File: dso_list
Created attachment 1527311 [details] File: exploitable
Created attachment 1527312 [details] File: limits
Created attachment 1527313 [details] File: maps
Created attachment 1527314 [details] File: mountinfo
Created attachment 1527315 [details] File: open_fds
Created attachment 1527316 [details] File: proc_pid_status
Thanks for a bug report. I see in the backtrace two other related threads to the crashing thread, all of them referencing session 0x560a83b257c0. Thread 1 is the crashing thread in ews_notification_soup_got_chunk(). Thread 2 is calling soup_session_abort(). Finally, Thread 17 is also inside ews_notification_soup_got_chunk(). The two threads with ews_notification_soup_got_chunk() are running on different messages, thus it should be fine. I do not see why the abort for the soup session had been called. Do you recall anything from the time of the crash, please? Maybe some change in connection, the Exchange server could not be contacted, or anything like that.
I don't recall any particulars, just saw this in abrt and reported it. The configured Exchange server is a bit weird - it only allows logins from the corporate network. Anything else gets login denied. Maybe I was leaving the corp wifi? I really don't know.
*** Bug 1728629 has been marked as a duplicate of this bug. ***
The above duplicate is from Fedora 30. It's similar, the crashing thread is processing a response from the server, while another thread is trying to stop the processing by unsubscribing from the receiving of the changes from the server. I'm wondering how much this is libsoup specific, like libsoup not being thread safe in this way. I'd like to know an opinion from someone of the upstream libsoup developers, but I do not know whom exactly to ask.
*** Bug 1728653 has been marked as a duplicate of this bug. ***
The bug #1728653 is not an exact duplicate, but it's quite close. It contains interesting var_log_messages, especially these: > jul 10 11:23:49 laptoprp evolution[3800]: object SoupAddress 0x55deff37e2e0 finalized while still in-construction > jul 10 11:23:49 laptoprp evolution[3800]: Custom constructor for class SoupAddress returned NULL (which is invalid). Please use GInitable instead.
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.