GNOME Bugzilla – Bug 712681
Calendar and address book stop working
Last modified: 2014-03-06 11:12:27 UTC
Both calendar and addressbook factories seem to stop working after a while, and never respond again until they're killed and restarted. I think it happens when I fall off the VPN. So perhaps it's related to bug 708175, where the mail side doesn't recover from a VPN disconnection either. But with mail, I can force it to work again by clicking to go offine and then online again. With calendar and addressbook, nothing works except killing the factories. Here's output of a defunct calendar server this morning, after the VPN session expired overnight. To make things worse, there is *no* indication in the UI that this has broken. I can click 'refresh' on the calendar, wondering why a meeting that I *know* have been added is not showing up. And nothing appears untoward. Apart from the continued absence of the new meeting. ... </m:SyncFolderItemsResponse> </s:Body> </s:Envelope> (evolution-calendar-factory:9742): e-cal-backend-caldav-WARNING **: Server did not response with 207, but with code 500 (Internal Server Error) ** (evolution-calendar-factory:9742): WARNING **: ews_start_sync_thread: No response: Cannot connect to destination (irsmsx103.ger.corp.intel.com) ** (evolution-calendar-factory:9742): WARNING **: ews_start_sync_thread: No response: Cannot resolve hostname (irsmsx103.ger.corp.intel.com) (evolution-calendar-factory:9742): e-cal-backend-caldav-WARNING **: Server did not response with 207, but with code 500 (Internal Server Error) (evolution-calendar-factory:9742): e-cal-backend-caldav-WARNING **: Server did not response with 207, but with code 500 (Internal Server Error) (evolution-calendar-factory:9742): e-cal-backend-caldav-WARNING **: Server did not response with 207, but with code 500 (Internal Server Error) (evolution-calendar-factory:9742): libedata-cal-CRITICAL **: e_data_cal_view_component_matches: assertion `E_IS_CAL_COMPONENT (component)' failed (evolution-calendar-factory:9742): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (evolution-calendar-factory:9742): libedata-cal-CRITICAL **: e_data_cal_view_component_matches: assertion `E_IS_CAL_COMPONENT (component)' failed (evolution-calendar-factory:9742): libedata-cal-CRITICAL **: e_data_cal_view_component_matches: assertion `E_IS_CAL_COMPONENT (component)' failed (evolution-calendar-factory:9742): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (evolution-calendar-factory:9742): libedata-cal-CRITICAL **: e_data_cal_view_component_matches: assertion `E_IS_CAL_COMPONENT (component)' failed (evolution-calendar-factory:9742): libedata-cal-CRITICAL **: e_data_cal_view_component_matches: assertion `E_IS_CAL_COMPONENT (component)' failed (evolution-calendar-factory:9742): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (evolution-calendar-factory:9742): libedata-cal-CRITICAL **: e_data_cal_view_component_matches: assertion `E_IS_CAL_COMPONENT (component)' failed (evolution-calendar-factory:9742): libedata-cal-CRITICAL **: e_data_cal_view_component_matches: assertion `E_IS_CAL_COMPONENT (component)' failed (evolution-calendar-factory:9742): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (evolution-calendar-factory:9742): libedata-cal-CRITICAL **: e_data_cal_view_component_matches: assertion `E_IS_CAL_COMPONENT (component)' failed (evolution-calendar-factory:9742): libedata-cal-CRITICAL **: e_data_cal_view_component_matches: assertion `E_IS_CAL_COMPONENT (component)' failed (evolution-calendar-factory:9742): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (evolution-calendar-factory:9742): libedata-cal-CRITICAL **: e_data_cal_view_component_matches: assertion `E_IS_CAL_COMPONENT (component)' failed (evolution-calendar-factory:9742): libedata-cal-CRITICAL **: e_data_cal_view_component_matches: assertion `E_IS_CAL_COMPONENT (component)' failed (evolution-calendar-factory:9742): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
The 3.10 has an online/offline icon indicator on the right of the calendar name in the calendar tree, same as the addressbook. I do not recall how much the functionality is done for a recover after the network connection lost though, but I recall Matthew did some fixes in this area for 3.11.x. I'd say "reopen if you see this with 3.12.0+".
*** Bug 712682 has been marked as a duplicate of this bug. ***