Description of problem: This happened while I had gnome-calendar open and toggled off the calendar for my Google account in gnome's online account panel of the gnome settings application. Version-Release number of selected component: gnome-calendar-3.30.1-1.fc29 Additional info: reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: /usr/bin/gnome-calendar --gapplication-service crash_function: g_atomic_ref_count_compare executable: /usr/bin/gnome-calendar journald_cursor: s=9d5facea53d6467e9428b74f2f11437b;i=12977a;b=e388fa13c88b417898533e3998138006;m=12102f2ca;t=57d889738ebaf;x=c8938578870f2024 kernel: 4.19.9-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_atomic_ref_count_compare at grefcount.c:284 #1 g_hash_table_lookup_node at ghash.c:1153 #2 g_hash_table_lookup at ghash.c:1153 #3 gcal_manager_is_client_writable at ../src/gcal-manager.c:1563 #4 on_source_changed at ../src/gcal-quick-add-popover.c:537 #9 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:2102 #10 _g_closure_invoke_va at gclosure.c:873 #13 source_registry_source_changed_idle_cb at /usr/src/debug/evolution-data-server-3.30.3-1.fc29.x86_64/src/libedataserver/e-source-registry.c:571 #18 g_main_context_iteration at gmain.c:3981 #19 g_application_run at gapplication.c:2470
Created attachment 1516143 [details] File: backtrace
Created attachment 1516144 [details] File: cgroup
Created attachment 1516145 [details] File: core_backtrace
Created attachment 1516146 [details] File: cpuinfo
Created attachment 1516147 [details] File: dso_list
Created attachment 1516148 [details] File: environ
Created attachment 1516149 [details] File: exploitable
Created attachment 1516150 [details] File: limits
Created attachment 1516151 [details] File: maps
Created attachment 1516152 [details] File: mountinfo
Created attachment 1516153 [details] File: open_fds
Created attachment 1516154 [details] File: proc_pid_status
Created attachment 1516155 [details] File: var_log_messages
*** Bug 1669495 has been marked as a duplicate of this bug. ***
*** Bug 1672111 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.