Bug 118977 - All events are 2 hours earlier in Calendar than they are in OWA
Summary: All events are 2 hours earlier in Calendar than they are in OWA
Status: RESOLVED DUPLICATE of bug 84229
Alias: None
Product: korganizer
Classification: Applications
Component: exchangeplugin (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Reinhold Kainhofer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-25 11:37 UTC by Bart Verwilst
Modified: 2006-03-05 17:34 UTC (History)
1 user (show)

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 Bart Verwilst 2005-12-25 11:37:39 UTC
Version:            (using KDE KDE 3.5.0)
Installed from:    Ubuntu Packages
OS:                Linux

When trying to log into the exchange server at work ( Exchange 2003 IIRC ), all events are perfectly shown, but they are all scheduled 2 hours early. Meetings that are planned from 8:00 to 10:00 happen from 6:00 to 8:00 according to korganizer. In OWA, the timezone is identical to my local timezone, and in OWA all the hours are correct.. I know it's now exchange 2000, but still, it's so close to fully working :D
Comment 1 Aaron Williams 2006-02-14 02:32:13 UTC
I am seeing the same problem, though they show up 7 hours after the meeting time.  I am running on Solaris with KDE 3.5.1.  Changing the timezone does not appear to make any difference.  I am in the US/Pacific timezone (or PST8PDT).
Comment 2 Stefan Haug 2006-02-17 13:05:27 UTC
Same problem for me using KDE 3.5.1 on SuSE 9.2 with Exchange 2003, all events are scheduled either 1 or 2 hours early, I'am running in CET timezone. Seems like the events are transfered in UTC and somehow not converted correctly to the local timezone.
Another interesting thing is that even if I move the event to the correct time in KOrganizer I still get the reminders for those events with the wrong time means 1 or 2 hours to early.
Comment 3 Thiago Macieira 2006-03-05 17:34:44 UTC

*** This bug has been marked as a duplicate of 84229 ***