Description of problem: normal startup and login Version-Release number of selected component: evolution-data-server-3.44.2-1.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Evolution\x2dalarm\x2dnotify-2157.scope cmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify crash_function: source_registry_object_added_no_owner executable: /usr/libexec/evolution-data-server/evolution-alarm-notify journald_cursor: s=4c60e764024d4b279719849b91ce0296;i=1d84;b=33e178eccaf3476a9b75021998654b52;m=1209f8889;t=5e0c8898c64c9;x=fedea2488884dec7 kernel: 5.17.12-300.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #9 source_registry_object_added_no_owner at /usr/src/debug/evolution-data-server-3.44.2-1.fc36.x86_64/src/libedataserver/e-source-registry.c:867 #10 source_registry_object_added_cb at /usr/src/debug/evolution-data-server-3.44.2-1.fc36.x86_64/src/libedataserver/e-source-registry.c:883 #12 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3743 #15 add_interfaces at ../gio/gdbusobjectmanagerclient.c:1670 #16 on_control_proxy_g_signal at ../gio/gdbusobjectmanagerclient.c:1784 #18 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3743 #21 on_signal_received at ../gio/gdbusproxy.c:895 #22 emit_signal_instance_in_idle_cb at ../gio/gdbusconnection.c:3788 #26 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4211 #28 source_registry_object_manager_thread at /usr/src/debug/evolution-data-server-3.44.2-1.fc36.x86_64/src/libedataserver/e-source-registry.c:1163
Created attachment 1887589 [details] File: backtrace
Created attachment 1887590 [details] File: core_backtrace
Created attachment 1887591 [details] File: cpuinfo
Created attachment 1887592 [details] File: dso_list
Created attachment 1887593 [details] File: environ
Created attachment 1887594 [details] File: limits
Created attachment 1887595 [details] File: maps
Created attachment 1887596 [details] File: mountinfo
Created attachment 1887597 [details] File: open_fds
Created attachment 1887598 [details] File: proc_pid_status
Thanks for a bug report. I checked the code and it doesn't show anything obvious. It's no big surprise, because it's a crash due to detected memory corruption, which can strike long after it happens. Are you able to reproduce this reliably, please? If you can, it would help to run the evolution-source-registry under valgrind, which can detect certain memory usage issues. First of all, install debuginfo packages for the evolution-data-server, thus the information provided by valgrind is usable. You can do it with this command: $ sudo dnf install evolution-data-server-debuginfo --enablerepo=updates-debuginfo Make sure the installed version precisely matches the version of the main package. You can verify that with: $ rpm -qa | grep evolution-data-server The commands to run the process under valgrind are these: $ export GIGACAGE_ENABLED=0 $ export WEBKIT_FORCE_SANDBOX=0 $ export Malloc=1 $ export G_SLICE=always-malloc $ valgrind --num-callers=30 --leak-check=no --track-origins=yes --aspace-minaddr=0x100000000 \ /usr/libexec/evolution-source-registry &>log.txt Even is the source registry won't crash, the log.txt can still contain information about the problem, because valgrind can avoid certain kinds of crashes and log about them instead. Unfortunately, if the problem depends on certain timing, the valgrind can prevent it as a side effect of all the memory checking (which is time consuming). I suggest ot have the source registry running under valgrind and then start Evolution or other application you use, which talks to the evolution-data-server processes, thus there will be done some activity on the source registry side.
Similar problem has been detected: install evolution... stop notificator reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Evolution\x2dalarm\x2dnotify-2239.scope cmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify crash_function: source_registry_object_added_no_owner executable: /usr/libexec/evolution-data-server/evolution-alarm-notify journald_cursor: s=f33618b73022440298bcc05db26e6780;i=c49b;b=b70d3664ff9f452c99713d6bdad805dc;m=11f01b0e;t=5e4d4aa8333c7;x=8aba3368ccd08456 kernel: 5.18.13-200.fc36.x86_64 package: evolution-data-server-3.44.3-1.fc36 reason: evolution-alarm-notify killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It just crashed reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/evolution-addressbook-factory.service cmdline: /usr/libexec/evolution-addressbook-factory crash_function: source_registry_object_added_no_owner executable: /usr/libexec/evolution-addressbook-factory journald_cursor: s=e4ccd30648ab49c782180ed1f163e478;i=5ded;b=2bfd33c8d32e4e00a166f6aad1aa3490;m=792749b67;t=5e5419f784210;x=461ed5a9f1d1b6b3 kernel: 5.18.13-200.fc36.x86_64 package: evolution-data-server-3.44.3-1.fc36 reason: evolution-addressbook-factory killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2135281 has been marked as a duplicate of this bug. ***
I see a similar crash happened within different processes. I named the evolution-source-registry process in comment #11, but in fact it can be used for nay process, where the crash happened.
*** Bug 2158634 has been marked as a duplicate of this bug. ***
I managed to figure out what the problem is and the upcoming 3.46.3 will contain a fix: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/0e447747229d4e76e6406ea338212d154b22b8a3
FEDORA-2023-23f3a72a0e has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-23f3a72a0e
*** Bug 2135278 has been marked as a duplicate of this bug. ***
*** Bug 2112202 has been marked as a duplicate of this bug. ***
*** Bug 2135326 has been marked as a duplicate of this bug. ***
*** Bug 2114057 has been marked as a duplicate of this bug. ***
*** Bug 2107756 has been marked as a duplicate of this bug. ***
*** Bug 2107832 has been marked as a duplicate of this bug. ***
FEDORA-2023-91adecfed5 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-91adecfed5
FEDORA-2023-91adecfed5 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-2023-91adecfed5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-91adecfed5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-23f3a72a0e has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-23f3a72a0e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-23f3a72a0e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-91adecfed5 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-23f3a72a0e has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.