Bug 86837

Summary:	Wrong time after syncing with SLOX
Product:	[Applications] korganizer	Reporter:	Daniel Bertolo <daniel.bertolo>
Component:	general	Assignee:	Cornelius Schumacher <schumacher>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Daniel Bertolo 2004-08-09 11:35:17 UTC

Version:           3.3 beta2 (using KDE 3.2.92 (3.3 beta2), SuSE)
Compiler:          gcc version 3.3.3 (SuSE Linux)
OS:                Linux (i686) release 2.6.5-7.95-default

I configured KOrganizer (in Kontact) to work with my SLOX server. Both server and client do use UTC (+1h for Switzerland +1h summer time). When I open KOrganizer, the timeline shows the correct time. After syncing with SLOX, it jumps two hours back. All events and todos from the server show wrong start and end times (also shifted by 2 hours). If I create a new event using KOrganizer, the times are shifted two hours in front on the server, showing the correct time in KOrganizer (but wrong on the webinterface).

Loaded plugins:
- Holiday plugin for calendars
- Project plugin for KOrganizer
- Web export plugin for KOrganizer

Comment 1 Daniel Bertolo 2004-08-09 11:43:46 UTC

I just found out, that our server is using local time, not UTC. This was my fault. But there could actually be a mechanism to check, what timezone the server uses in order to communicate with different clients. It should not matter whetever I use UTC or not. Changing the client to local time would probably solve the problem. But IMO KOrganizer should handle this.

Comment 2 Cornelius Schumacher 2004-08-09 13:34:20 UTC

The timeline problem should be fixed with RC1. Timezones should now be handled correctly.

The server doesn't provide access to the timezone setting, so the client can't do much about different timezone settings on the server and the client, but the times are consistent and can be brought into sync by using the same setting on both sides. Internally they are exclusively handled as UTC anyway.