Bug 237949

Summary:	Dissociate From Recurrence broken
Product:	[Applications] korganizer	Reporter:	Tassilo Horn <tassilo>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Tassilo Horn 2010-05-17 18:01:02 UTC

Version:            (using KDE 4.4.3)
OS:                Linux
Installed from:    Gentoo Packages

I have quite a lot recurring events (weekly on a given day).  Usually, when creating such an event, I don't know when it will end or any exceptions, and so I don't specify such things.

I guess, the "Dissociate From Recurrence..." context menu entry is exactly for conveniently adding an exception or an end date depending on a user's choice in the "Only dissociate this one" (Exception) / "Also dissociate future ones" (end date) dialog.

Both dissociation types are totally broken in KDE 4.4.3.

Here's a recipe for the end date usecase:

  1. Create a new event Bar recurring every Tueday.
  2. Jump forward one week and select that event.
  3. Select "Dissociate from Recurrence..." -> "Also dissociate future ones"

In the summary, the event still shows up in any future week.

When checking the properties of the Bar event I've just dissociated, there is no exception nor an end date.
When checking the properties of the first Bar event (in the previous week), this one now has an end date set: the Monday before the Tuesday from which on I dissociated...

Checking the std.ics file, there are 2 VEVENTs for Bar now.  One with end date and one without.

What it should have done in this "Also dissociate future ones" use case was to add an end date to the existing entry.

(I'll add a recipe for the bug in the "Only dissociate this one" usecase later...)

Comment 1 Tassilo Horn 2010-05-17 21:07:35 UTC

Here's a recipe for the broken "Only dissociate this one" behavior:

1. Create a new weekly recurring event "Baz".
2. Jump forward one week and select that event.
3. Select "Dissociate from Recurrence..." -> "Only dissociate this one"

Expected result: The one single Baz event has one exception for that date.

Actual result: There's a new duplicate Baz event on that day which has no reccurence set.  The original Baz event has one exception for the day I've dissolved.

Comment 2 Tassilo Horn 2010-05-17 21:26:14 UTC

As you can see, in both usecases the "Dissolve From Recurrence" should only modify the existing event, either by adding an end date or an exception.
The creation of a duplicate event is wrong in both cases.

This bug together with bug 172464 and bug 223388 make korganizer really hard to use for me.  Not that I don't know workarounds, but I hardly TRUST korganizer anymore.  And that 2 month after I switched all my PIM needs to KDE/Kontact...

Till I recognized that there is a bug in korganizer I used the dissolve feature quite some time.  When I saw that there's something wrong, I ended up fixing and compacting (removing dups) the iCal file manually with a text editor.

KOrganizer has so many features which simply don't work or at least you cannot be sure they work.  So currently I refrain to use anything that has to do with drag&drop or shortcut features in the context menu, but always go through the event properties.

Comment 3 Tassilo Horn 2010-05-18 09:34:03 UTC

Argh, I think this is not a bug but the correct behavior.  After looking up the exact definition of "dissociate" the current behavior makes sense to me.

Sorry for the noise.