Version: 3.5.6 (using KDE 3.5.9) Installed from: SuSE RPMs OS: Linux If I add a recurring event on Feb 29 recurring every Year. I can only see it in Years with a 29. Feb. on all other Years its missing. It is better to view it on March 1 (in Years without Feb 29.). So I dont't miss that appointment (e.g. a birthday). See bug reports: http://bugs.kde.org/show_bug.cgi?id=40194 (this one http://bugs.kde.org/show_bug.cgi?id=74365 might be related) How to reproduce: - schedule an event without time associated on feb 29 2008 - The event must recur each year on the 29 of februari Now check the event on the next years 2009, 2010, 2011 and 2012. In 2009-2011 it is not present neither on 1 march, on 29 feb it is back
I can still reproduce this on trunk r865573.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
I reported the bug. I'm running kontact at version 4.14, as such I can't test the way you requested. I assume that you're running KDE at version 5 or later. But this bug should be easily reproducible. Let me repeat it from initial problem description: How to reproduce, but updated for recent years: - Schedule an event without time associated on feb 29 2016 in korganizer ( - The event must recur each year on the 29 of February The solution might be a warning when the event is scheduled. Now check the event on the next years 2017, 2018, 2019 and 2020. In 2019-2019 it is not present neither on 1 march, on 29 feb 2020 it is back.
Richard, you are right. I just tested it myself. And there should definitely be some feedback for this.
Denis you're my hero. Thanks for looking into the KDE bug situation and for verying this problem.
This behavior is not a bug. The Internet Calendaring standard (https://tools.ietf.org/html/rfc5545#section-3.3.10) says Recurrence rules may generate recurrence instances with an invalid date (e.g., February 30) or nonexistent local time (e.g., 1:30 AM on a day where the local time is moved forward by an hour at 1:00 AM). Such recurrence instances MUST be ignored and MUST NOT be counted as part of the recurrence set. Current versions of KOrganizer give you a choice: - Recur on February 29th only (i.e. only in leap years) - Recur on the last day of February (the 28th in non-leap years) - Recur on the 60th day of the year (March 1st in non-leap years)