Description of problem: When running gnome-calendar, it fails to come up most of the time. When tried from a terminal, it says: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Remote peer disconnected Version-Release number of selected component (if applicable): gnome-calendar-3.34.0-1.fc31.x86_64 How reproducible: Sometimes Steps to Reproduce: 1. Run from "activites": won't always come up 2. Run from terminal: gives error and doesn't come up 3. Actual results: Does not always come up Expected results: Should always come up Additional info: Reported upstream: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/455
I can reproduce this behaviour, too. It is confirmed by the coredumpctl: ==== Thu 2019-09-19 14:13:29 CEST 2481 1000 1000 11 present /usr/bin/gnome-calendar Thu 2019-09-19 14:16:02 CEST 3084 1000 1000 11 present /usr/bin/gnome-calendar ==== The journalctl related logs: ==== Sep 19 14:16:01 localhost.localdomain systemd[1686]: dbus-:1.2-org.gnome.Calendar: Succeeded. Sep 19 14:16:01 localhost.localdomain systemd[1686]: dbus-:1.2-org.gnome.Calendar: Consumed 1.346s CPU time. Sep 19 14:16:02 localhost.localdomain systemd-coredump[3390]: Process 3084 (gnome-calendar) of user 1000 dumped core. Stack trace of thread 3084: #0 0x00007f909553faad g_slice_alloc (libglib-2.0.so.0) #1 0x00007f90955444b8 g_string_sized_new (libglib-2.0.so.0) #2 0x00007f90955238d0 add_to_partial (libglib-2.0.so.0) #3 0x00007f90955255b1 g_markup_parse_context_parse (libglib-2.0.so.0) #4 0x00007f9095e5af0e _gtk_builder_parser_parse_buffer (libgtk-3.so.0) #5 0x00007f9095e55091 gtk_builder_add_from_resource (libgtk-3.so.0) #6 0x00007f9095e5860c gtk_builder_new_from_resource (libgtk-3.so.0) #7 0x00007f9095e3efb0 gtk_application_window_added (libgtk-3.so.0) #8 0x00007f909560ee43 g_cclosure_marshal_VOID__OBJECTv (libgobject-2.0.so.0) #9 0x00007f909560b996 _g_closure_invoke_va (libgobject-2.0.so.0) #10 0x00007f9095628228 g_signal_emit_valist (libgobject-2.0.so.0) #11 0x00007f90956289d3 g_signal_emit (libgobject-2.0.so.0) #12 0x00007f90960cf428 gtk_window_set_application (libgtk-3.so.0) #13 0x00007f90956117c1 g_object_new_internal (libgobject-2.0.so.0) #14 0x00007f9095613338 g_object_new_valist (libgobject-2.0.so.0) #15 0x00007f909561368d g_object_new (libgobject-2.0.so.0) #16 0x000055c92b30bfd6 gcal_application_activate (gnome-calendar) #17 0x00007f909560b996 _g_closure_invoke_va (libgobject-2.0.so.0) #18 0x00007f9095628228 g_signal_emit_valist (libgobject-2.0.so.0) #19 0x00007f9095628fc9 g_signal_emit_by_name (libgobject-2.0.so.0) #20 0x00007f9095739d1d g_application_impl_method_call (libgio-2.0.so.0) #21 0x00007f90957631c4 call_in_idle_cb (libgio-2.0.so.0) #22 0x00007f909551ddcb g_idle_dispatch (libglib-2.0.so.0) #23 0x00007f90955214a0 g_main_context_dispatch (libglib-2.0.so.0) #24 0x00007f9095521830 g_main_context_iterate.isra.0 (libglib-2.0.so.0) #25 0x00007f90955218d3 g_main_context_iteration (libglib-2.0.so.0) #26 0x00007f9095737bc5 g_application_run (libgio-2.0.so.0) #27 0x000055c92b309432 main (gnome-calendar) #28 0x00007f90950171a3 __libc_start_main (libc.so.6) #29 0x000055c92b3094ce _start (gnome-calendar) Stack trace of thread 3132: #0 0x00007f90950e6a1f __poll (libc.so.6) #1 0x00007f909552179e g_main_context_iterate.isra.0 (libglib-2.0.so.0) #2 0x00007f90955218d3 g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f9095521921 glib_worker_main (libglib-2.0.so.0) #4 0x00007f909554af52 g_thread_proxy (libglib-2.0.so.0) #5 0x00007f90917414e2 start_thread (libpthread.so.0) #6 0x00007f90950f1643 __clone (libc.so.6) Stack trace of thread 3169: #0 0x00007f90950e6a1f __poll (libc.so.6) #1 0x00007f909552179e g_main_context_iterate.isra.0 (libglib-2.0.so.0) #2 0x00007f9095521b23 g_main_loop_run (libglib-2.0.so.0) #3 0x00007f909594af9f source_registry_object_manager_thread (libedataserver-1.2.so.24) #4 0x00007f909554af52 g_thread_proxy (libglib-2.0.so.0) #5 0x00007f90917414e2 start_thread (libpthread.so.0) #6 0x00007f90950f1643 __clone (libc.so.6) Stack trace of thread 3171: #0 0x00007f90950e6a1f __poll (libc.so.6) #1 0x00007f909552179e g_main_context_iterate.isra.0 (libglib-2.0.so.0) #2 0x00007f9095521b23 g_main_loop_run (libglib-2.0.so.0) #3 0x00007f9095a38ed8 cal_client_dbus_thread (libecal-2.0.so.1) #4 0x00007f909554af52 g_thread_proxy (libglib-2.0.so.0) #5 0x00007f90917414e2 start_thread (libpthread.so.0) #6 0x00007f90950f1643 __clone (libc.so.6) Stack trace of thread 3142: #0 0x00007f90950e6a1f __poll (libc.so.6) #1 0x00007f909552179e g_main_context_iterate.isra.0 (libglib-2.0.so.0) #2 0x00007f90955218d3 g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f908a4f293d dconf_gdbus_worker_thread (libdconfsettings.so) #4 0x00007f909554af52 g_thread_proxy (libglib-2.0.so.0) #5 0x00007f90917414e2 start_thread (libpthread.so.0) #6 0x00007f90950f1643 __clone (libc.so.6) Stack trace of thread 3134: #0 0x00007f90950e6a1f __poll (libc.so.6) #1 0x00007f909552179e g_main_context_iterate.isra.0 (libglib-2.0.so.0) #2 0x00007f9095521b23 g_main_loop_run (libglib-2.0.so.0) #3 0x00007f909577364a gdbus_shared_thread_func (libgio-2.0.so.0) #4 0x00007f909554af52 g_thread_proxy (libglib-2.0.so.0) #5 0x00007f90917414e2 start_thread (libpthread.so.0) #6 0x00007f90950f1643 __clone (libc.so.6) Stack trace of thread 3388: #0 0x00007f90950ec15d syscall (libc.so.6) #1 0x00007f909556dc26 g_cond_wait_until (libglib-2.0.so.0) #2 0x00007f90954f2411 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0) #3 0x00007f909554b7ea g_thread_pool_thread_proxy (libglib-2.0.so.0) #4 0x00007f909554af52 g_thread_proxy (libglib-2.0.so.0) #5 0x00007f90917414e2 start_thread (libpthread.so.0) #6 0x00007f90950f1643 __clone (libc.so.6) Sep 19 14:16:02 localhost.localdomain systemd[1]: systemd-coredump: Succeeded. Sep 19 14:16:02 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-3389-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 19 14:16:02 localhost.localdomain dleyna-renderer-service[3382]: dLeyna: Exit Sep 19 14:16:02 localhost.localdomain systemd[1686]: dbus-:1.2-com.intel.dleyna-renderer: Succeeded. Sep 19 14:16:03 localhost.localdomain abrt-server[3398]: Lock file '.lock' is locked by process 2119 Sep 19 14:16:03 localhost.localdomain abrt-notification[3437]: Process 3084 (gnome-calendar) crashed in g_slice_alloc() ====
Proposed as a Blocker for 31-final by Fedora user lruzicka using the blocker tracking app because: Gnome Calendar is one of the default application and it is crucial that it works correctly, otherwise user experience is not good. I am proposing this as a blocker because, in my belief it violates: Default application functionality: All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test. All applications installed by default in Fedora Workstation must comply with each MUST and MUST NOT guideline in the Applications and Launchers policy.
I'm going to have an update out in a sec. Please give it a little more testing than usual because, while it fixes the issue for me, the backtrace I was getting was different than the one reported here. I think that's expected due to the nature of the crash (a double-free, they don't always crash immediately). But if I'm wrong, there could be another issue here.
FEDORA-2019-803a45c6a0 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-803a45c6a0
gnome-calendar-3.34.0-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-803a45c6a0
Actually I think the crash on startup that I fixed in that update is different. This one actually looks more like https://gitlab.gnome.org/GNOME/gnome-calendar/issues/417.
Please let me know if this 3.34.0-2.fc31 fixes it or not. If so, I'll close this bug.
Gnome-calendar seems to start fine now, so I guess this is fixed. Thanks very much :)