Version-Release number of selected component: evolution-3.46.1-1.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cmdline: evolution crash_function: soup_connection_auth_free_connection_state dso_list: /usr/bin/evolution evolution-3.46.1-1.fc37.x86_64 (Fedora Project) 1668727230 executable: /usr/bin/evolution journald_cursor: s=0e3f89d25ed64095a046cc4e142a4ffa;i=1b392;b=3488d517888d48c099a6b1e5b82d69ef;m=b20aafa08;t=5edf02b15fc34;x=780ea03b27fb4b83 kernel: 6.0.8-300.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 soup_connection_auth_free_connection_state at ../libsoup/auth/soup-connection-auth.c:43 #1 connection_disconnected at ../libsoup/auth/soup-connection-auth.c:55 #2 _g_closure_invoke_va at ../gobject/gclosure.c:895 #5 soup_connection_list_disconnect_all at ../libsoup/soup-connection-manager.c:292 #6 soup_connection_manager_get_connection_locked at ../libsoup/soup-connection-manager.c:420 #7 soup_connection_manager_get_connection at ../libsoup/soup-connection-manager.c:502 #8 soup_session_ensure_item_connection at ../libsoup/soup-session.c:1696 #9 soup_session_process_queue_item at ../libsoup/soup-session.c:1747 #10 async_run_queue at ../libsoup/soup-session.c:1854 #11 queue_dispatch at ../libsoup/soup-session.c:187
Created attachment 1925989 [details] File: backtrace
Created attachment 1925990 [details] File: cgroup
Created attachment 1925991 [details] File: core_backtrace
Created attachment 1925992 [details] File: cpuinfo
Created attachment 1925993 [details] File: environ
Created attachment 1925994 [details] File: exploitable
Created attachment 1925995 [details] File: limits
Created attachment 1925996 [details] File: maps
Created attachment 1925997 [details] File: mountinfo
Created attachment 1925998 [details] File: open_fds
Created attachment 1925999 [details] File: proc_pid_status
Created attachment 1926000 [details] File: var_log_messages
Thanks for a bug report. This seems to be deep in the libsoup3 code. Could you get the current version of that package, please? You can see it when you run: $ rpm -q libsoup3
No problem! This is the output: ``` $ rpm -q libsoup3 libsoup3-3.2.2-1.fc37.x86_64 ```
Thanks. It looks like a variant of [1]. [1] https://gitlab.gnome.org/GNOME/evolution/-/issues/2137
Created attachment 1931307 [details] patch to test Could any of you try to install this [1] scratch build, then restart the machine and let it running for some time, please? The test build contains this attached patch, which tries to add thread safety to the related libsoup3 object. You can install the package with: sudo dnf update https://kojipkgs.fedoraproject.org//work/tasks/4962/95124962/libsoup3-3.2.2-1.2.x86_64.rpm If you've installed more libsoup3 packages, then you'll need to update all of them at once. The scratch build will disappear in a week or so, I'm not sure of precise time. It'll be good to have the machine running for some time. I'll be gone till the end of the year, thus no problem from my side, just the opposite, it's ideal if you could run with it for the next few weeks. [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=95124962
Not sure if it's gonna be any help, but I've installed the RPM file you linked. If any further crashes occur, I will report back. Thanks for looking into the matter!
I have also installed the RPM file linked. Sofar no crash ..
Thank you both. I guess it did not crash yet (or you've not been using Evolution "extensively" during the holiday season). I offered the change upstream, as part of an existing similar crash report: https://gitlab.gnome.org/GNOME/libsoup/-/issues/317
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.