Version-Release number of selected component: evolution-data-server-3.46.0-1.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/evolution-source-registry.service cmdline: /usr/libexec/evolution-source-registry crash_function: g_mutex_lock executable: /usr/libexec/evolution-source-registry journald_cursor: s=202dfa61c1b342d99dd8dd09ca58ccbe;i=11efe;b=2f964f1ecc454fe6b106dbf52a23d070;m=5798433cc;t=5eb2e0741dea2;x=512367b4778db6c8 kernel: 5.19.14-300.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_mutex_lock at ../glib/gthread-posix.c:1529 #1 soup_connection_manager_cleanup.isra.0 at ../libsoup/soup-connection-manager.c:516 #2 async_run_queue at ../libsoup/soup-session.c:1821 #3 queue_dispatch at ../libsoup/soup-session.c:184 #6 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4238 #8 dbus_server_run_server at /usr/src/debug/evolution-data-server-3.46.0-1.fc37.x86_64/src/libebackend/e-dbus-server.c:317 #9 ffi_call_unix64 at ../src/x86/unix64.S:105 #10 ffi_call_int at ../src/x86/ffi64.c:672 #11 g_cclosure_marshal_generic_va at ../gobject/gclosure.c:1650 #12 _g_closure_invoke_va at ../gobject/gclosure.c:895
Created attachment 1918373 [details] File: backtrace
Created attachment 1918374 [details] File: core_backtrace
Created attachment 1918375 [details] File: cpuinfo
Created attachment 1918376 [details] File: dso_list
Created attachment 1918377 [details] File: environ
Created attachment 1918378 [details] File: exploitable
Created attachment 1918379 [details] File: limits
Created attachment 1918380 [details] File: maps
Created attachment 1918381 [details] File: mountinfo
Created attachment 1918382 [details] File: open_fds
Created attachment 1918383 [details] File: proc_pid_status
Thanks for a bug report. This crash had been fixed upstream, under the libsoup project, recently: https://gitlab.gnome.org/GNOME/libsoup/-/issues/308 The next release of the libsoup library, the 3.2.2 version, will contain the fix. I do not know when precisely the release will be done.
*** Bug 2140239 has been marked as a duplicate of this bug. ***
FEDORA-2022-4c75b2cdf9 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4c75b2cdf9
FEDORA-2022-4c75b2cdf9 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-4c75b2cdf9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4c75b2cdf9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-4c75b2cdf9 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.