Bug 285405

Summary: Exceptions in occurence: problem with ics format?
Product: [Applications] korganizer Reporter: kaouete <kaouete>
Component: recurrenceAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: 4.7   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description kaouete 2011-10-31 16:38:10 UTC 
Version:           4.7 (using KDE 4.7.2) 
OS:                Linux

Hi,

I have been using korganizer with akonadi groupware connector.
I sync with a SOGo caldav server.

I don't think the problem is directly linked to SOGo or akonadi, but it is where it is visible.

Reproducible: Always

Steps to Reproduce:

The problem is as following:

If I add a recurring event for 5 consecutive days in korganizer, the ical content is as follow (as given by akonadi console in the raw payload field):
BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML libkcal 3.2//EN
VERSION:2.0
BEGIN:VEVENT
CREATED:20111031T162950Z
ORGANIZER;CN="Victor Noël":MAILTO:victor.noel@irit.fr
DTSTAMP:20111031T162929Z
UID:8dba3f03-2888-4d3e-9e7c-e4b7d7e9c0fd
LAST-MODIFIED:20111031T162929Z
SUMMARY:Test Rec
RRULE:FREQ=DAILY;COUNT=5
DTSTART;TZID=Europe/Paris:20111107T170000
DTEND;TZID=Europe/Paris:20111107T180000
TRANSP:OPAQUE
END:VEVENT

END:VCALENDAR

Then, if I add an exception from korganizer for the 2nd day, the content is as follow:
BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML libkcal 3.2//EN
VERSION:2.0
BEGIN:VEVENT
CREATED:20111031T163056Z
ORGANIZER;CN="Victor Noël":MAILTO:victor.noel@irit.fr
DTSTAMP:20111031T162929Z
UID:8dba3f03-2888-4d3e-9e7c-e4b7d7e9c0fd
SEQUENCE:1
LAST-MODIFIED:20111031T162929Z
SUMMARY:Test Rec
RRULE:FREQ=DAILY;COUNT=5
EXDATE;VALUE=DATE:20111108
DTSTART;TZID=Europe/Paris:20111107T170000
DTEND;TZID=Europe/Paris:20111107T180000
TRANSP:OPAQUE
END:VEVENT

END:VCALENDAR

In particular the "EXDATE;VALUE=DATE:20111108" should be noticed.

But, with this information, the exception is not shown in SOGo or on my phone where I sync too (this is why I started investigating this thing :).

Now, if I decide to add an exception from SOGo, this is the content of the event:
BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML libkcal 3.2//EN
VERSION:2.0
BEGIN:VEVENT
CREATED:20111031T163228Z
ORGANIZER;CN="Victor Noël":MAILTO:victor.noel@irit.fr
DTSTAMP:20111031T162929Z
UID:8dba3f03-2888-4d3e-9e7c-e4b7d7e9c0fd
SEQUENCE:2
LAST-MODIFIED:20111031T162929Z
SUMMARY:Test Rec
RRULE:FREQ=DAILY;COUNT=5
EXDATE;VALUE=DATE:20111108
EXDATE:20111109T160000Z
DTSTART;TZID=Europe/Paris:20111107T170000
DTEND;TZID=Europe/Paris:20111107T180000
TRANSP:OPAQUE
END:VEVENT

END:VCALENDAR

Notice the newly added line and the way it is formatted.
EXDATE:20111109T160000Z

Now, everywhere this exception is shown: in SOGo, on my phone and in korganizer.
Also, in korganizer, the previously added exception is still present, and if I edit the event (for all recurrence), then I can ONLY see the first exception in the exception list and not the one added from SOGo.


Expected Results:  
So, based on that, it seems to me that there is two problems with korganizer:
1) the way it store the exception information is incorrect, or at least not the standard way (or SOGo and android calendar are wrong, this must be verified first).
2) exceptions shown in the calendar must also be visible in the edit window.

I'm available to do more tests if necessary :)

Thank you very much!
Comment 1 kaouete 2011-10-31 16:45:51 UTC 
Hi, here is an  additional comment:

According to this:
http://www.sogo.nu/bugs/view.php?id=1355

While my previous comments still hold, the format used for the date itself in korganizer seems to be the correct one!
Comment 2 kaouete 2011-10-31 16:57:30 UTC 
Hi,

Another comment:

According to this:
http://www.sogo.nu/bugs/view.php?id=867

It is possible that the 1st point I noted as a bug isn't one, but the second one still holds.

Also, since VALUE=DATE is optional, if it is not needed, maybe it would be better to not use it in order to be compatible with limited clients?
I don't know, I will anyway report these matters to the clients I know of :)
Thank you!
Comment 3 kaouete 2011-10-31 18:14:32 UTC 
Sorry, actually about my first comment about the bug (http://www.sogo.nu/bugs/view.php?id=1355) from SOGo is wrong.
This bug refers to all-day events while mine isn't one.

But timezone should not be specified at least.

Thanks and sorry for the noise :)
Comment 4 Denis Kurz 2016-09-24 18:47:53 UTC 
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.
Comment 5 Denis Kurz 2017-01-07 21:48:43 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.