Bug 64342

Additional comments: 
This is similiar to 60573, but the description and cause/effect 
were different enough I felt it should be reported. 

Subject: Re: Receiving incoming Exchange ICS changes korig timezone

Thanks for the bug report. 
What I didn't quite understand: Does the event change the timezone of 
korganizer itself, or does the event just appear shifted (i.e. not 2am 
Central Time, but 2am UTC)? 
In particular, is only the received event affected, or the whole application? 

To me it would be clear if the event appears shifted, because it uses a 
VTIMEZONE and the TZID tag in the DTSTART field, which is not yet supported 
by libkcal. However, your reports seems to indicate that korganizer changes 
its own time zone and thus shifts all events.

Or did I misunderstand something here?

Thanks,
Reinhold

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/m9LATqjEwhXvPN0RAoyrAKDKv9ZoPMjMot8i2t/Gfl4THrt2FACgx+lJ
AFtA4fFGLVqS0oQZ9TRJ+/Q=
=r1Vp
-----END PGP SIGNATURE-----

Its been a few weeks since I've run that test, so
from memory... The red time line actually
does shift, so that may indicate the apps itself changes
its time.  The schedule of existing events does not change
(ie:  something at 2pm before is still at 2pm after).
The new event will (I think) show up at the correct time,
but any upload of that event will be in the wrong timezone,
and in general things just start going down hill trying
to sync to Outlook.  

I'll re-run the test again and send anything more specific.

I re-ran this test.  With the current time at 1:15pm US/Central,
I entered the calendar record below.  The red-line system time
immediately jumped to 7:15pm.  When I opened the incoming message,
the table showed 1:30pm-2:00 (correct), and when I accepted the
meeting, it was placed at the correct time slots.  The redline
remained in the 7:15pm hour.  I then closed the program and restarted
it and the system time was then correct, and the meeting still
showed in the correct time slot.

Another thing I've noticed.  The same time shifting can occur
if an event is uploaded to Exchange; where the red line will shift.
One needs to be careful as the uploaded event may cause some
corruption to an existing Exchange event if the timezones
are incorrect.  I do it, but I typically restart korg between
each step to make sure the timezones are in sync.

Forgot to add the calendar entry from the above comments...


BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft CDO for Microsoft Exchange
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Central Time (US & Canada)
X-MICROSOFT-CDO-TZID:11
BEGIN:STANDARD
DTSTART:16010101T020000
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=4;BYDAY=1SU
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20031028T191056Z
DTSTART;TZID="Central Time (US & Canada)":20031028T133000
SUMMARY:Test Meeting
UID:{965D4D1F-EA34-4654-8A27-473AB8646C88}
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Foddy, Br
 ian K":MAILTO:brian.foddy@nwa.com
ORGANIZER;CN="Foddy, Brian K":MAILTO:brian.foddy@nwa.com
LOCATION:
DTEND;TZID="Central Time (US & Canada)":20031028T140000
DESCRIPTION:\NTest meeting\N
SEQUENCE:1
PRIORITY:5
CLASS:
CREATED:20031028T191055Z
LAST-MODIFIED:20031028T191056Z
STATUS:CONFIRMED
TRANSP:OPAQUE
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-OWNERAPPTID:-1
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR

*** Bug 59693 has been marked as a duplicate of this bug. ***

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

Brian¸ if you're still following this bug, can you re-try with recent KOrganizer?  I'm working on this bug to solve https://bugzilla.novell.com/show_bug.cgi?id=238093 .  
I've saved the above ical from #5 to a file and set it up as a local file resource, and the timezone is now interpreted correctly - however KOrganizer reports a parse error when saved in .kde/share/apps/korganizer/income.accepted.

Thanks, my kde has become a bit dated so I can't try the fix very soon.
Thanks for working on it tho.

Brian


Will Stephenson wrote:

[bugs.kde.org quoted mail]

Brian> any news ?

sorry, my machine is still stuck on Solaris 8 and I don't want to attempt a kde
upgrade until we get to 10.  Perhaps by the end of the year.

Thanks for checking.
Brian

I've tried to import the event from comment #5. 
The time setted on the event is:
1:30am
2:00pm
and the timezone is "floating".

Moreover it is shown only in month view.

(tested using current KDE4 trunk on OpenSuse)

Doesn't seem to be Solaris specific.

I tested in KDE 4.4 and the event appears in agenda view at 19h30 which is correct for me, I live at GMT: 13h30@GMT-6 == 19h30@GMT.

Please retest.