Bug 236563

Summary: When editing text notes of recurring items, Korganizer modifies all future items and deletes all past items
Product: [Applications] korganizer Reporter: Dotan Cohen <kde-2011.08>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: major CC: andreas, awinnenb, bugz, wstephenson, yehielb
Priority: NOR    
Version: 4.4.2   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Dotan Cohen 2010-05-06 13:05:14 UTC
Version:            (using KDE 4.4.2)
Installed from:    Unspecified Linux

When editing the text note of a weekly recurring item Korganizer modifies all future items and deletes all past items. This is a severe dataloss bug.
Comment 1 Dj YB 2010-05-06 16:40:27 UTC
just checked it on fc11 4.4.2 on a daily recurring events, when editing the second day all the days moved forward to that point.
like if the previous recurring event was deleted and a new one generated in its place starting from that edited day.

clearly not the desired (intuitive) result.
thanks,
YB.
Comment 2 Dotan Cohen 2010-05-07 14:26:16 UTC
Likely related:
https://bugs.kde.org/show_bug.cgi?id=234088
Comment 3 Dotan Cohen 2010-05-07 16:40:09 UTC
I can confirm this on a brand new KDE 4.4.3 install and a clean ~/.kde as well.
Comment 4 Drew Winnenberg 2010-05-07 23:41:51 UTC
I can confirm on 4.4.3, with a carryover .kde from 4.3 series.
Comment 5 Andreas Mahel 2010-05-08 21:36:00 UTC
I can confirm this behavior on OpenSuSE 11.2, KDE 4.4.3
To me, this looks like a duplicate of https://bugs.kde.org/show_bug.cgi?id=226394
Comment 6 bugz 2010-05-27 07:53:10 UTC
I'm experiencing this bug as well, and it is extremely destructive.  I've lost all all sorts of repeating events.  The software is clearly unusable now, and should be rolled back.  It's insane that such a severe and clearly repeatable problem would be re-published.
Comment 7 Will Stephenson 2010-06-22 09:47:31 UTC
Dupe as per #5

*** This bug has been marked as a duplicate of bug 226394 ***