Bug 270697 - The UNTIL of repeating events loses one day every time you exit korganizer
Summary: The UNTIL of repeating events loses one day every time you exit korganizer
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: recurrence (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-11 17:58 UTC by bert
Modified: 2017-01-07 22:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description bert 2011-04-11 17:58:58 UTC 
Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

(Korganizer version 4.4.7)

It seems very often when korganizer modifies the std.ics file, it subtracts one day from the UNTIL date of all repeating events. They get shorter and shorter and the UNTIL date can even become earlier than the DTSTART date.

Reproducible: Always

Steps to Reproduce:
Create a daily-repeating event with an end date (*not* a number of occurrences) and exit korganizer. Start korganizer again, open the event for editing and notice that the repeating event has become one day shorter.

Actual Results:  
The repeating event gets one day shorter.

Expected Results:  
The repeating event keeps the same number of days.

OS: Linux (x86_64) release 2.6.32-5-amd64
Compiler: cc
Comment 1 Sergio Martins 2011-04-11 20:05:36 UTC 
Working fine in master.
Comment 2 Denis Kurz 2016-09-24 18:52:36 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 3 Denis Kurz 2017-01-07 22:37:15 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.