Description of problem: Now that Akonadi supports CalDAV, I tried switching to KOrganizer today (from Thunderbird+Lightning) and configured it to use my Zimbra calendar over CalDAV. I noticed a few recurring meetings were missing from my calendar. They show up once on September 15 and 16, and if I open them the Recurrence tab shows "Repeat: Never". Zimbra, Thunderbird, and Evolution all display the events correctly, but KOrganizer seems confused. Version-Release number of selected component (if applicable): kdepim-4.7.2-5.fc16.x86_64 How reproducible: unknown Steps to Reproduce: 1. Connect KOrganizer to a Zimbra server using CalDAV 2. Look at recurring meetings Actual results: some recurring meetings only show once in KOrganizer Expected results: all recurring meetings are shown Additional info:
Created attachment 529401 [details] ics of missing recurring meeting I used Konqueror and connected to the Zimbra server using WebDAV so I could see my calendar as individual ics files. With a bit of grep'ing, I found the ics file for my missing recurring meeting. I see something interesting about this file that's different from the hundreds of other ICS files: there are 2 almost identical VEVENT entries but only the first one has an RRULE. $ egrep 'VEVENT|RRULE' bad-recurrence.ics <snip timezones> BEGIN:VEVENT RRULE:FREQ=WEEKLY END:VEVENT BEGIN:VEVENT END:VEVENT I've attached the full bad-recurrence.ics file here (with meeting details stripped out, obviously). My other missing recurring meetings also have 2 VEVENTs but only one RRULE. I don't know the iCalendar standard well enough to say if this is bad syntax or not, but Zimbra, Thunderbird+Lightning and Evolution all show the meetings correctly.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
This is still an issue with Fedora 18 and KDE 4.9.5, and the external bug is still valid.
This is still an issue with Fedora 19 and KDE 4.10.95.
Has an upstream bug been opened? If so, could anyone post the link to the bug here, please?
There's patch for this issue at KDE reviewboard: https://git.reviewboard.kde.org/r/113374/ But still, the patch needs further work: 1) issues raised in the review 2) with the patch, I still don't see exceptional instances of the recurring events
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The original review seems dead, so I opened a new one for the patch few weeks ago: https://git.reviewboard.kde.org/r/114357/ However, the patch is causing massive memory leaks upon every calendar refresh, so this issue needs to be sorted.
I, too, am seeing this problem in F20.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.