Bug 219316 - Recurring events are not handled correctly
Summary: Recurring events are not handled correctly
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: GoogleData Resource (show other bugs)
Version: 4.3
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Adenilson Cavalcanti
URL:
Keywords:
: 223198 248958 272114 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-12-19 15:30 UTC by Vedran Furač
Modified: 2017-01-07 22:10 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vedran Furač 2009-12-19 15:30:51 UTC
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Debian testing/unstable Packages

It connects successfully and downloads something (333B long) but not the whole calendar. OTOH, syncing google contacts works. Here's debug log:

0x1896b40 34 BEGIN 
0x1896b40 34 OK Begin completed 
0x1896b40 35 X-AKLSUB 0 INF (RESOURCE "akonadi_gcal_resource_0") 
0x1896b40 * 4 0 (NAME "akonadi_gcal_resource_0" MIMETYPE (text/calendar) REMOTEID "google-calendar" RESOURCE "akonadi_gcal_resource_0" CACHEPOLICY (INHERIT true INTERVAL -1 CACHETIMEOUT -1 SYNCONDEMAND false LOCALPARTS (ALL)) ) 
0x1896b40 35 OK List completed 
0x1896b40 36 MODIFY 4 MIMETYPE (text/calendar) PARENT 0 NAME "akonadi_gcal_resource_0" REMOTEID "google-calendar" 
0x1896b40 36 OK MODIFY done 
0x1896b40 37 COMMIT 
0x1896b40 37 OK Commit completed 
0x1896b40 38 X-AKLSUB 0 INF (RESOURCE "akonadi_gcal_resource_0") 
0x1896b40 * 4 0 (NAME "akonadi_gcal_resource_0" MIMETYPE (text/calendar) REMOTEID "google-calendar" RESOURCE "akonadi_gcal_resource_0" CACHEPOLICY (INHERIT true INTERVAL -1 CACHETIMEOUT -1 SYNCONDEMAND false LOCALPARTS (ALL)) ) 
0x1896b40 38 OK List completed 
0x1896b40 39 SELECT SILENT 4 
0x1896b40 39 OK Completed 
0x1896b40 40 FETCH 1:* FULLPAYLOAD ALLATTR CACHEONLY EXTERNALPAYLOAD (UID REMOTEID COLLECTIONID FLAGS SIZE DATETIME) 
0x1896b40 * 1 FETCH (UID 1 REV 0 REMOTEID "http://www.google.com/calendar/feeds/default/private/full/t72aih9pkb71c057v0nefc6g0c" MIMETYPE "text/calendar" COLLECTIONID "4" SIZE 333 DATETIME "19-Dec-2009 01:51:29 +0000" FLAGS () PLD:RFC822 {333} BEGIN:VCALENDAR PRODID:-//K Desktop Environment//NONSGML libkcal 3.2//EN VERSION:2.0 BEGIN:VEVENT DTSTAMP:20091219T015129Z CREATED:20091219T015129Z UID:libkcal-1949988800.736 LAST-MODIFIED:20091219T015129Z SUMMARY:blahprivate LOCATION:noneedtoknow STATUS:CONFIRMED DTSTART:-4713010T000000 TRANSP:OPAQUE END:VEVENT END:VCALENDAR) 
0x1896b40 40 OK FETCH completed
Comment 1 Vedran Furač 2010-03-10 03:44:43 UTC
In fact it "works". I have only repeated events in my calendar and those are not displayed properly in korganiser.
Comment 2 Tobias Koenig 2010-08-02 19:10:14 UTC
*** Bug 223198 has been marked as a duplicate of this bug. ***
Comment 3 Tobias Koenig 2010-09-02 19:01:16 UTC
*** Bug 248958 has been marked as a duplicate of this bug. ***
Comment 4 Tobias Klein 2010-10-24 17:06:09 UTC
Apparently this seems to be an issue of libgcal:
http://code.google.com/p/libgcal/issues/detail?id=18#c6

The code for the bug fix is currently under review, so hopefully this is gonna be fixed soon :-)
http://gitorious.org/libgcal/libgcal/merge_requests/1
Comment 5 Javier Ruere 2011-01-21 18:32:08 UTC
*** This bug has been confirmed by popular vote. ***
Comment 6 Christophe Marin 2011-07-10 15:50:19 UTC
*** Bug 272114 has been marked as a duplicate of this bug. ***
Comment 7 Denis Kurz 2016-09-24 20:32:29 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 8 Denis Kurz 2017-01-07 22:10:19 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.