Bug 112186

Summary:	regression: vcard adds incorrectly in version 3.4, ok in 3.1.1
Product:	[Applications] korganizer	Reporter:	Gerry Cocco <gerry>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version First Reported In:	3.4
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Gerry Cocco 2005-09-07 22:24:23 UTC

Version:           3.4 (using KDE KDE 3.4.0)
Installed from:    Fedora RPMs
OS:                Linux

The following vcard "merges" correctly into my Korganizer 3.1.1, but merges incorrectly on v3.4.  It seems to be related to the "VTIMEZONE" paragraph being present, since the older VCARD format using "TZ:+0000" (and no VTIMEZONE) works on both.   With the "VTIMEZONE" paragraph, the item is entered on the following day as a 1-2AM meeting.  Looks like it could be something to do with the timezone not being applied, or being applied twice.    I stripped down the test case as much as I could.  The original is (obviously) from Lotus Notes.  

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Lotus Development Corporation//NONSGML Notes 7.0//EN

BEGIN:VTIMEZONE
TZID:Central
BEGIN:STANDARD
DTSTART:19501029T020000
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19500402T020000
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=1SU;BYMONTH=4
END:DAYLIGHT
END:VTIMEZONE

BEGIN:VEVENT
DTSTART;TZID="Central":20051204T190000
DTEND;TZID="Central":20051204T200000
CLASS:PUBLIC
SUMMARY:Meeting applies OK in Korganizer 3.1.1
UID:1FE8D3F8894E2C7386257071000558E1-Lotus_Notes_Generated
END:VEVENT

END:VCALENDAR

Comment 1 Reinhold Kainhofer 2006-11-02 18:52:54 UTC

Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.

Comment 2 Denis Kurz 2016-09-24 18:45:53 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:01:11 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.