Version-Release number of selected component: gnome-shell-43.0-3.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Shell.CalendarServer cmdline: /usr/libexec/gnome-shell-calendar-server crash_function: source_registry_object_added_no_owner executable: /usr/libexec/gnome-shell-calendar-server journald_cursor: s=202dfa61c1b342d99dd8dd09ca58ccbe;i=12281;b=2f964f1ecc454fe6b106dbf52a23d070;m=d9447f27a;t=5eb362221a494;x=8f5724c9c8375df7 kernel: 5.19.14-300.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 2112202
Created attachment 1918458 [details] File: backtrace
Created attachment 1918459 [details] File: core_backtrace
Created attachment 1918460 [details] File: cpuinfo
Created attachment 1918461 [details] File: dso_list
Created attachment 1918462 [details] File: environ
Created attachment 1918463 [details] File: limits
Created attachment 1918464 [details] File: maps
Created attachment 1918465 [details] File: mountinfo
Created attachment 1918466 [details] File: open_fds
Created attachment 1918467 [details] File: proc_pid_status
Similar problem has been detected: Just installer evolution and evolution-ows and it happened in the background. Had accounts (Exchange, Microsoft, NextCloud) already configured in the Gnome settings. reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Shell.CalendarServer cmdline: /usr/libexec/gnome-shell-calendar-server crash_function: source_registry_object_added_no_owner executable: /usr/libexec/gnome-shell-calendar-server journald_cursor: s=50a2a56d034d4a159905c938ec1625d4;i=1d6aa;b=bed475c1a37048229a834f837864cebc;m=1de7e882;t=5ee0cc7769220;x=a5d7b423fa4b7391 kernel: 6.0.9-300.fc37.x86_64 package: gnome-shell-43.1-3.fc37 reason: gnome-shell-calendar-server killed by SIGABRT rootdir: / runlevel: N 3 type: CCpp uid: 1000
*** Bug 2158638 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 2094417 ***