Most iCals I get do not contain an explicit timezone specification. Also kOrganizer itself does not seem to include a timezone specification when exporting events from the local timezone (Europe/Berlin for me). (Not tested for events in different time zones.) Upon import, these events are treated as being in UTC instead of "Floating" or "local timezone", interpreting all timestamps as shifted by a few hours. Reproducible: Always Expected Results: kOrganizer should consistently import and export events such that a "roundtrip" of exporting, deleting and re-importing the event does not modify its dates and times. This is a regression, as I never had problems with this in kOrganizer 3.x or 4.x. In addition kOrganizer should import "common" iCals in a way expected by the user.
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Behaviour seems to have changed a bit. Events seem to be imported correctly. What I noticed is that an event sent from the calendar using right-click -> "Send as iCalendar" is sent with start/end times converted to UTC instead of being sent in the specified time zone. This way, at least timezone information is lost. I'd also expect some possibly unwanted side-effects in regard to DST, but didn't try this in more detail.
Created attachment 106284 [details] iCalendar file as exported from kOrganizer via right-click -> "Send as iCalendar". The original event eas specified in CEST, TZ Europe/Berlin.
The same happens with KOrganizer version 5.3.0 (QtWebEngine): The original libkcal file in ~/.local/share/korganizer contains: DTSTART;TZID=Europe/Berlin:20170918T200000 DTEND;TZID=Europe/Berlin:20170918T213000 The iCal file sent via KMail2 contains: DTSTART:20170918T180000Z DTEND:20170918T193000Z Q.E.D.
On the other hand, KOrganizer/4.14 was also doing this: The original libkcal file in ~/.local/share/korganizer contains: TZID:Europe/Berlin TZNAME:CET DTSTART;TZID=Europe/Berlin:20170629T200000 DTEND;TZID=Europe/Berlin:20170629T213000 The iCal file sent via KMail (KDE4) contains: DTSTART:20170629T180000Z DTEND:20170629T193000Z
(In reply to Don Curtis from comment #4) > The same happens with KOrganizer version 5.3.0 (QtWebEngine): > > The original libkcal file in ~/.local/share/korganizer contains: > DTSTART;TZID=Europe/Berlin:20170918T200000 > DTEND;TZID=Europe/Berlin:20170918T213000 > > The iCal file sent via KMail2 contains: > DTSTART:20170918T180000Z > DTEND:20170918T193000Z > > Q.E.D. See also https://bugs.kde.org/show_bug.cgi?id=373988 Seems actually more appropriate and possibly the central cause.
KOrganizer version 5.5.2: Calender entries which are imported from an iCal file exported from KOrganizer running on another machine are missing the following information in the ~/.local/share/korganizer/<Calendar directory>/ libkcal-xxxxx file: BEGIN:VTIMEZONE TZID:Europe/Berlin *** for example . . . *** END:VTIMEZONE The libkcal-xxx file generated from the imported iCal file simply begin with a "BEGIN:VEVENT" section and do not contain any time zone information for the calendar event.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Seems to work properly now.