Calendar: Handle errors in file backend's refresh thread gracefully
I regularly notice that I have no calendar events in gnome-shell or gnome-calendar. When this happens, I have to reboot my computer to see calendar events again. In gnome-calendar, I also have no visible calendars displayed:
@feaneron suggests something is wrong with evolution-data-server. How to debug it when this happens?
systemctl --user status evolution-calendar-factory.service
says:
● evolution-calendar-factory.service - Evolution calendar service
Loaded: loaded (/usr/lib/systemd/user/evolution-calendar-factory.service; static; vendor preset: enabled)
Active: active (running) since Sat 2019-12-07 12:36:46 CST; 23h ago
Main PID: 21239 (evolution-calen)
Tasks: 11 (limit: 76964)
Memory: 8.6M
CPU: 207ms
CGroup: /user.slice/user-1000.slice/user@1000.service/evolution-calendar-factory.service
└─21239 /usr/libexec/evolution-calendar-factory
Dec 07 12:36:46 chargestone-cave systemd[1701]: Starting Evolution calendar service...
Dec 07 12:36:46 chargestone-cave systemd[1701]: Started Evolution calendar service.
Dec 07 17:13:43 chargestone-cave evolution-calen[21239]: refresh_thread_func: assertion 'info != NULL' failed
Today is Dec 08, but I think I didn't shut down my computer last night, so if the issue in refresh_thread_func() is to blame, then maybe it failed after running for five hours?
Edited by Milan Crha