Bug 352977 - kMail (kOrganizer?) 5.0.x Regression: ICal Invitations displayed with wrong event time in mail reader
Summary: kMail (kOrganizer?) 5.0.x Regression: ICal Invitations displayed with wrong e...
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: UI (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-21 11:27 UTC by Gunter Ohrner
Modified: 2017-06-25 09:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gunter Ohrner 2015-09-21 11:27:17 UTC
Received iCal event's start / end times are displayed shifted by one hour in the mail viewer.

One example contains the following event time information, generated by MS Exchange:

DTSTART;TZID=W. Europe Standard Time:20150924T150000
DTEND;TZID=W. Europe Standard Time:20150924T180000

The event's time and duration is displayed as "16:00 - 19:00". Local timezone according to KDE Systemsettings is "Europe/Berlin (LMT)". (Whatever "LMT" might mean...)

After importing it into the kOrganizer calendar, the resulting event is shown with correct start and end times (15:00 - 18:00).

Reproducible: Always
Comment 1 Denis Kurz 2017-06-23 20:16:30 UTC
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.
Comment 2 Gunter Ohrner 2017-06-25 09:18:33 UTC
Seems to be fixed in 5.5.2.