Description of problem: Added a new calendar entry to a calendar hosted with google calendars. Version-Release number of selected component: gnome-calendar-3.26.2-1.fc27 Additional info: reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-calendar --gapplication-service crash_function: GCAL_IS_MANAGER executable: /usr/bin/gnome-calendar journald_cursor: s=01d0dc94c90e46c89e4dc8a349600c0c;i=1caee;b=4ced0eca7abb40e8a59b6b8735b0a25d;m=f10961bce;t=55d292c013d55;x=6e3eebb216bcfbb9 kernel: 4.13.9-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 GCAL_IS_MANAGER at ../src/gcal-manager.h:34 #1 gcal_manager_get_default_source at ../src/gcal-manager.c:1213 #2 update_default_calendar_row at ../src/gcal-quick-add-popover.c:487 #8 g_object_notify_queue_thaw at gobject.c:296 #9 g_object_setv at gobject.c:2248 #10 g_object_set_property at gobject.c:2529 #11 on_source_notify at gbinding.c:327 #17 g_object_notify_by_spec_internal at gobject.c:1173 #23 g_settings_real_change_event at gsettings.c:386 #24 ffi_call_unix64 at ../src/x86/unix64.S:76
Created attachment 1347785 [details] File: backtrace
Created attachment 1347786 [details] File: cgroup
Created attachment 1347787 [details] File: core_backtrace
Created attachment 1347788 [details] File: cpuinfo
Created attachment 1347789 [details] File: dso_list
Created attachment 1347790 [details] File: environ
Created attachment 1347791 [details] File: exploitable
Created attachment 1347792 [details] File: limits
Created attachment 1347793 [details] File: maps
Created attachment 1347794 [details] File: open_fds
Created attachment 1347795 [details] File: proc_pid_status
Created attachment 1347796 [details] File: var_log_messages
*** Bug 1541045 has been marked as a duplicate of this bug. ***
*** Bug 1557941 has been marked as a duplicate of this bug. ***
Similar problem has been detected: THis happened right after I clicked the calendar icon. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-calendar --gapplication-service crash_function: GCAL_IS_MANAGER executable: /usr/bin/gnome-calendar journald_cursor: s=5f3d04c3f1a54ee0b90e3c4e3f9fd96d;i=1218b9;b=d230e6da970a40749d67ec4282238c90;m=741c117;t=5688b439f1fd7;x=c01267c3dcf8d98a kernel: 4.15.13-300.fc27.x86_64 package: gnome-calendar-3.26.4-1.fc27 reason: gnome-calendar killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Added an item to the calendar reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-calendar --gapplication-service crash_function: GCAL_IS_MANAGER executable: /usr/bin/gnome-calendar journald_cursor: s=8f73a211e4794d21bcdb22bf564ceb03;i=3b40;b=d7fd05417d7649bfb78851bb722e2a5c;m=1f71980a08;t=5698a2ef70a3e;x=8e0d0c8208654a83 kernel: 4.15.14-300.fc27.x86_64 package: gnome-calendar-3.26.4-1.fc27 reason: gnome-calendar killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Please test with latest updates and reopen if still reproducible.
Reopening since this is still crashing in 3.32.
*** Bug 1723983 has been marked as a duplicate of this bug. ***
Looks like gcal_quick_add_popover_set_property() is failing to disconnect its signals from the old GCalManager before setting the new one.
Looking at the backtrace in bug #1723983, I see the GcalManager emitting the signal is 0x559bdefff130 but the GcalQuickAddPopover's current manager is 0x559bdf1fe0e0, which is surely unintended. Now, I think there might be a separate bug here, because that shouldn't be enough to crash as the GcalQuickAddPopover's GcalManager *should* still be a valid GcalManager. So I suspect the GcalQuickAddPopover itself is invalid at this point. So it looks like two bugs: (a) need to disconnect in gcal_quick_add_popover_set_property(), and (b) also need to use g_signal_connect_object() to disconnect on dispose.
*** Bug 1680240 has been marked as a duplicate of this bug. ***
*** Bug 1695107 has been marked as a duplicate of this bug. ***
*** Bug 1685974 has been marked as a duplicate of this bug. ***
*** Bug 1696649 has been marked as a duplicate of this bug. ***
*** Bug 1721817 has been marked as a duplicate of this bug. ***
*** Bug 1720854 has been marked as a duplicate of this bug. ***
*** Bug 1717077 has been marked as a duplicate of this bug. ***
*** Bug 1671587 has been marked as a duplicate of this bug. ***
*** Bug 1683362 has been marked as a duplicate of this bug. ***
*** Bug 1673089 has been marked as a duplicate of this bug. ***
*** Bug 1648105 has been marked as a duplicate of this bug. ***
*** Bug 1665783 has been marked as a duplicate of this bug. ***
*** Bug 1671360 has been marked as a duplicate of this bug. ***
*** Bug 1678914 has been marked as a duplicate of this bug. ***
*** Bug 1727201 has been marked as a duplicate of this bug. ***
*** Bug 1728377 has been marked as a duplicate of this bug. ***
FEDORA-2019-ff61b597f3 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ff61b597f3
gnome-calendar-3.32.2-2.fc30 has been pushed to the Fedora 30 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-ff61b597f3
FEDORA-2019-ff0223e2ca has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ff0223e2ca
gnome-calendar-3.32.2-3.fc30 has been pushed to the Fedora 30 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-ff0223e2ca
gnome-calendar-3.32.2-4.fc30 has been pushed to the Fedora 30 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-ff0223e2ca
gnome-calendar-3.32.2-5.fc30 has been pushed to the Fedora 30 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-ff0223e2ca
gnome-calendar-3.32.2-5.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.