Bug 209541

Summary:	Akonadi iCal resource cannot be reloaded/refreshed
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Patrick <mail>
Component:	ICal file resource	Assignee:	kdepim bugs <kdepim-bugs>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	gvenour, info, smartins, torsten.crass
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Unspecified
Latest Commit:		Version Fixed In:

Description Patrick 2009-10-05 17:53:27 UTC

Version:            (using KDE 4.3.1)
Installed from:    Gentoo Packages

I am trying to get my Google calendar into Kontact/KOrganizer.

Therefore I specified the URL https://www.google.com/calendar/ical/<account>/.../basic.ics in the "Select Calendar - Akonadi Resource" dialogue window. It seemed to work fine, but updates to the Google calendar (which are immediately reflected in the .ICS file that can be downloaded under the above URL) do not appear in Kontact.

"Reload" (after right-click on the Akonadi resource) makes all calendar entries disappear until I restart Kontact (but then the new events still don't show up).
Editing the Akonadi resource, choosing the "akonadi_ical_resource_1" and clicking the "Synchronise Folder" button also doesn't help.

In bug #133614 I read that CalDAV-support is on the way, but until then it would be nice if Kontact could at least *show* an ICS calendar in a useful manner.

Comment 1 Alvin 2009-10-14 09:53:16 UTC

This bug look broader than only akonadi_ical resources. If you reload any akonadi resource (ical, gcal), all calendar entries disappear.

Comment 2 Torsten Crass 2009-11-07 19:33:36 UTC

Same here with most recent Debian Sid packages (i.e. akonadi-server 1.2.1-1 and korganizer 4.3.2-1). I have an iCal stored on an ftp server as only Akonadi sub-resource -- local changes get stored on the server, but remote changes don't show up locally. Also, all entries disappear when reloading either the Akonadi main resource or the iCal resource via right-click.

Regards --

tcrass

Comment 3 Sumit Madan 2010-12-09 19:34:05 UTC

*** This bug has been confirmed by popular vote. ***