GNOME Bugzilla – Bug 394633
Web calendar not updating
Last modified: 2012-06-18 16:19:43 UTC
Please describe the problem: Upon first logging-in to Gnome, Evolution and the clock/calendar applet show appointments from a subscribed web calendar correctly. Subsequent changes to that calendar, through a different interface, are not seen unless the evolution-data-server process is killed. When this process restarts new calendar entries can be seen. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
what refresh time did you set on your calendar in evolution ? default is 12h so you have to wait that long the see the changes.
I'd set it to 5 min, but set it to 1 min when I was testing to see whether it'd work.
Could you please confirm if this bug is still happening at your end ? Please try in 2.24.x / 2.26.x and report back, thanks.
It seems that this bug is still present in evolultion 2.26.3 (FC11). In fact, its worse. Given multiple evolution accounts on different workstations to the same caldav account, entries entered by one station are not seen by the others, unless you remove the account and reenter is again. Only the first sync is correct. The caldav server gets updated all right. All entries are there.
This might be fixed with bug #494394, whose patch had a little bug in itself, which was fixed only recently with this commit: http://git.gnome.org/browse/evolution-data-server/commit/?id=3bf185dbe87 With that user can right-click on the calendar in evolution's Calendar view and choose "Refresh", which will initiate a refresh. It can take some time till the CalDAV backend receives changes from the server, but it will work in general. The refresh does nothing if the calendar is currently updating its local cache. All these changes are part of 3.4.0 of evolution-data-server. Is anybody able to confirm this on that or any later version, please?
I forgot to add, similar applies for On The Web calendars, it has also available the Refresh popup menu item/functionality.
Please feel free to reopen the bug if the problem still occurs with a newer version of Evolution 3.4.2 or later, thanks.