KOrganizer 4.10 worked OK. After upgrade to 4.11 it didn't show any recurring events at all. Had to stab ~/.kde/share/apps/korganizer/std.ics manually to fix events. I removed all RECURRENCE-ID lines. This fixed many recurring events. Then there was some entries with: COMMENT:NoStartDate DTSTART:-4713010T000000 These where fixed by removing the COMMENT line and setting the DTSTART to have a VALUE like: DTSTART;VALUE=DATE:20100312 There are still probably some recurring events which are not show or they show incorrectly. e.g. only single event is shown but it is not recurring probably because RECURRENCE-ID was removed and there is no RRULE. Reproducible: Always
Possibly related issue #219316
Snipplets from diff output to show what manual changes where made Simple RECURRENCE-ID removal fix: BEGIN:VTODO ORGANIZER;CN=xxx DTSTAMP:20130801T200331Z CREATED:20130801T200331Z UID:KOrganizer-778175805.617 SEQUENCE:16 LAST-MODIFIED:20130801T200331Z SUMMARY:xxx PRIORITY:5 -RECURRENCE-ID;TZID=Europe/Mariehamn:20111121T000000 RRULE:FREQ=MONTHLY;INTERVAL=2;BYMONTHDAY=1 EXDATE;VALUE=DATE:20110103 DUE;TZID=Europe/Mariehamn:20120801T000000 DTSTART;TZID=Europe/Mariehamn:20100913T000000 PERCENT-COMPLETE:0 X-KDE-LIBKCAL-DTRECURRENCE;VALUE=DATE-TIME;TZID=Europe/Mariehamn: 20131001T000000 END:VTODO Including DTSTART fix: BEGIN:VTODO ORGANIZER;CN=xxx DTSTAMP:20130912T182219Z -COMMENT:NoStartDate CREATED:20130912T182219Z UID:KOrganizer-1768581676.415 SEQUENCE:95 LAST-MODIFIED:20130912T182219Z SUMMARY:xxx PRIORITY:5 -RECURRENCE-ID:20111212T000000 RRULE:FREQ=MONTHLY;BYMONTHDAY=12 DUE;VALUE=DATE:20100312 -DTSTART:-4713010T000000 +DTSTART;VALUE=DATE:20100312 PERCENT-COMPLETE:0 X-KDE-LIBKCAL-DTRECURRENCE;VALUE=DATE-TIME:20131012T000000 END:VTODO
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.
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.