I have a recurring event, created during wintertime with start=10:00UTC and end=11:00UTC. I am testing this right now (during summertime, CEST), as the result is likely to depend on the local timezone. Now there are several display issues with the event: Right-Click -> Show => "Time: 11.00 - 12.00" Should be: "Time:12.00 - 13.00" Display on the left and Tooltip: "Time: 12.00" Should be: "Time:12.00 - 13.00" Editor: "Time: 11.00 - 12.00 Timezone: Europe/Zurich" Should be: "Time:10.00 - 11.00 UTC" Note that the event is correctly displayed in the Day-Timetable view. When checking during wintertime (in January): Right-Click -> Show => "Time: 11.00 - 12.00" Correct Display on the left and Tooltip: "Time: 00.00" Should be: "Time:12.00 - 13.00" Editor: same as above The "Display on the left" only shows the invalid data after clicking on the event. When just clicking somewhere in the timetable view, it displays the correct information. (See screenshot) The editor issue is probably related to: https://bugs.kde.org/show_bug.cgi?id=308169 Reproducible: Always Steps to Reproduce: 1. Check the attached ics file
Created attachment 74454 [details] Recurring UTC event showing the problem
Created attachment 74455 [details] Screenshot illustrating the data shown after selecting the recurring event.
Created attachment 74456 [details] Same occurence showing the correct data after clicking next to the event
Since the editor issue has been fixed meanwhile, there is only one inconsistency left: If the event is recurring, and stored in UTC, it is moved correctly in the calendar view by one hour over the DST change, but the sidebar view and the "show" option display the event with the currently active DST offset (as opposed to the one applicable to the currently selected time in the calendar). So if I have an event at 10:00 UTC, which recurs at 11:00 in my timezone without DST, and I look at it when DST applies, I get: - 12:00 in the calendar (correct) - 11:00 in the sidebar, the "show" view and the tooltip (should probably also be 12:00 I think)
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.
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.