Bug 354908 - Recurring events are missing on a caldav resource (Zimbra)
Summary: Recurring events are missing on a caldav resource (Zimbra)
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: recurrence (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-05 16:59 UTC by davidebasilio
Modified: 2018-01-31 17:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description davidebasilio 2015-11-05 16:59:59 UTC
I have a caldav calendar set up in Korganizer 5.0.2.
The calendar works OK, except all recurring meetings are not shown, which is a rather big problem, since I have quite a few of those.

I did some search and there seem to be old reports about the same issue:

https://bugzilla.redhat.com/show_bug.cgi?id=747755
https://bugs.kde.org/show_bug.cgi?id=284884


Reproducible: Always

Steps to Reproduce:
Add a caldav resource

Actual Results:  
recurring events do not appear

Expected Results:  
all events should be there
Comment 1 Tim Eberhardt 2015-12-02 18:13:22 UTC
I can confirm this Bug with version 5.0.3 (Gentoo)
Comment 2 Denis Kurz 2017-06-23 20:18:58 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-01-31 17:14:52 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.