Bug 349173 - timezone Europe/Amsterdam problems/corrupt
Summary: timezone Europe/Amsterdam problems/corrupt
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-15 09:20 UTC by Sander van Grieken
Modified: 2018-01-31 17:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sander van Grieken 2015-06-15 09:20:48 UTC
When I create an Event in KOrganizer using timezone Europe/Amsterdam, the generated ICS has very strange timezone definitions.

Both DAV and ICS files resources generate the data below, which confuses (amongst others) other clients that access the CalDAV resource (shifted 40 minutes later, usually, but I've seen other difference values).

If I use Europe/Brussels, which is equivalent as far as I know, things work as expected..


BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Europe/Amsterdam
BEGIN:DAYLIGHT
TZNAME:NST
TZOFFSETFROM:+1932
TZOFFSETTO:+011932
DTSTART:19160501T000000
RDATE;VALUE=DATE-TIME:19160501T000000
RDATE;VALUE=DATE-TIME:19170416T020000
RDATE;VALUE=DATE-TIME:19180401T020000
RDATE;VALUE=DATE-TIME:19190407T020000
RDATE;VALUE=DATE-TIME:19200405T020000
RDATE;VALUE=DATE-TIME:19210404T020000
RDATE;VALUE=DATE-TIME:19220326T020000
RDATE;VALUE=DATE-TIME:19230601T020000
RDATE;VALUE=DATE-TIME:19240330T020000
RDATE;VALUE=DATE-TIME:19250605T020000
RDATE;VALUE=DATE-TIME:19260515T020000
RDATE;VALUE=DATE-TIME:19270515T020000
RDATE;VALUE=DATE-TIME:19280515T020000
RDATE;VALUE=DATE-TIME:19290515T020000
RDATE;VALUE=DATE-TIME:19300515T020000
RDATE;VALUE=DATE-TIME:19310515T020000
RDATE;VALUE=DATE-TIME:19320522T020000
RDATE;VALUE=DATE-TIME:19330515T020000
RDATE;VALUE=DATE-TIME:19340515T020000
RDATE;VALUE=DATE-TIME:19350515T020000
RDATE;VALUE=DATE-TIME:19360515T020000
RDATE;VALUE=DATE-TIME:19370522T020000
END:DAYLIGHT
BEGIN:STANDARD
TZNAME:AMT
TZOFFSETFROM:+011932
TZOFFSETTO:+1932
DTSTART:19231007T030000
RRULE:FREQ=YEARLY;COUNT=10;BYMONTH=10;BYDAY=1SU
END:STANDARD
BEGIN:STANDARD
TZNAME:AMT
TZOFFSETFROM:+011932
TZOFFSETTO:+1932
DTSTART:19161001T000000
RDATE;VALUE=DATE-TIME:19161001T000000
RDATE;VALUE=DATE-TIME:19170917T030000
RDATE;VALUE=DATE-TIME:19180930T030000
RDATE;VALUE=DATE-TIME:19190929T030000
RDATE;VALUE=DATE-TIME:19200927T030000
RDATE;VALUE=DATE-TIME:19210926T030000
RDATE;VALUE=DATE-TIME:19221008T030000
RDATE;VALUE=DATE-TIME:19331008T030000
RDATE;VALUE=DATE-TIME:19341007T030000
RDATE;VALUE=DATE-TIME:19351006T030000
RDATE;VALUE=DATE-TIME:19361004T030000
END:STANDARD
BEGIN:DAYLIGHT
TZNAME:NEST
TZOFFSETFROM:+011932
TZOFFSETTO:+0120
DTSTART:19370701T000000
RDATE;VALUE=DATE-TIME:19370701T000000
END:DAYLIGHT
BEGIN:STANDARD
TZNAME:NET
TZOFFSETFROM:+0120
TZOFFSETTO:+0020
DTSTART:19371003T030000
RDATE;VALUE=DATE-TIME:19371003T030000
RDATE;VALUE=DATE-TIME:19381002T030000
RDATE;VALUE=DATE-TIME:19391008T030000
END:STANDARD
BEGIN:DAYLIGHT
TZNAME:NEST
TZOFFSETFROM:+0020
TZOFFSETTO:+0120
DTSTART:19380515T020000
RDATE;VALUE=DATE-TIME:19380515T020000
RDATE;VALUE=DATE-TIME:19390515T020000
END:DAYLIGHT
BEGIN:DAYLIGHT
TZNAME:CEST
TZOFFSETFROM:+0020
TZOFFSETTO:+0200
DTSTART:19400516T000000
RDATE;VALUE=DATE-TIME:19400516T000000
END:DAYLIGHT
BEGIN:STANDARD
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19790930T030000
RRULE:FREQ=YEARLY;COUNT=17;BYMONTH=9;BYDAY=-1SU
END:STANDARD
BEGIN:STANDARD
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19961027T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
BEGIN:STANDARD
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19421102T030000
RDATE;VALUE=DATE-TIME:19421102T030000
RDATE;VALUE=DATE-TIME:19431004T030000
RDATE;VALUE=DATE-TIME:19441002T030000
RDATE;VALUE=DATE-TIME:19450916T030000
RDATE;VALUE=DATE-TIME:19770925T030000
RDATE;VALUE=DATE-TIME:19781001T030000
END:STANDARD
BEGIN:DAYLIGHT
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19810329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:DAYLIGHT
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19430329T020000
RDATE;VALUE=DATE-TIME:19430329T020000
RDATE;VALUE=DATE-TIME:19440403T020000
RDATE;VALUE=DATE-TIME:19450402T020000
RDATE;VALUE=DATE-TIME:19770403T020000
RDATE;VALUE=DATE-TIME:19780402T020000
RDATE;VALUE=DATE-TIME:19790401T020000
RDATE;VALUE=DATE-TIME:19800406T020000
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20150615T090551Z
CREATED:20150615T090551Z
UID:f3141f91-ff3b-44d4-b704-306c6e5b81ee
LAST-MODIFIED:20150615T090551Z
SUMMARY:test8
DTSTART;TZID=Europe/Amsterdam:20150615T160000
DTEND;TZID=Europe/Amsterdam:20150615T170000
TRANSP:OPAQUE
CLASS:PUBLIC
END:VEVENT
X-KDE-ICAL-IMPLEMENTATION-VERSION:1.0
END:VCALENDAR

Reproducible: Always
Comment 1 Denis Kurz 2017-06-23 19:59:35 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.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 oportunity 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 Denis Kurz 2018-01-31 17:13:37 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.