6.0.0-beta1
7/3/25

[#7628] Timezone problem on sync with synthesis
Summary Timezone problem on sync with synthesis
Queue Synchronization
Type Bug
State No Feedback
Priority 2. Medium
Owners jan (at) horde (dot) org
Requester stefan (at) pluecken (dot) de
Created 11/02/2008 (6087 days ago)
Due
Updated 12/04/2009 (5690 days ago)
Assigned 10/26/2009 (5729 days ago)
Resolved 12/04/2009 (5690 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
12/04/2009 03:41:44 PM Jan Schneider State ⇒ No Feedback
 
10/26/2009 06:53:29 PM Jan Schneider Comment #6
Taken from Karsten Fourmont
State ⇒ Feedback
Reply to this comment
I can't reproduce this. This event correctly creates a start time at 
12:00 CET when importing with the current git code.
12/07/2008 06:53:47 PM Jan Schneider State ⇒ Assigned
 
11/06/2008 12:03:36 PM stefan (at) pluecken (dot) de Comment #5 Reply to this comment
Changing the parameter in conf.php to

$conf['calendar']['params']['utc'] = false;

syncs correctly. So I think there is some localtime converting even 
when times are stored in UTC somewhere in the code.
11/06/2008 11:28:25 AM stefan (at) pluecken (dot) de Comment #4 Reply to this comment
Yes, the 12:00-13:00 is the appointment, that I added on the PDA. It 
shows up as 13:00-14:00 in Horde. I have tried it again by changing 
the time to something different, sync, then changing it back to 
12:00-13:00, sync again and it still shows up as 13:00-14:00 while the 
/tmp/sync/data.txt reads:

DTSTART:20081106T110000Z

DTEND:20081106T120000Z



Kronolith conf.php reads:

$conf['calendar']['params']['utc'] = true;

[Show Quoted Text - 22 lines]
11/06/2008 11:15:39 AM Jan Schneider Comment #3 Reply to this comment
Are you sure that you sent me exactly the log from your example below? 
The log show the following event coming from the client:



BEGIN:VCALENDAR

VERSION:1.0

BEGIN:VEVENT

SUMMARY:Test

CLASS:PUBLIC

DESCRIPTION:

DTSTART:20081106T110000Z

DTEND:20081106T120000Z

TRANSP:0

AALARM:20081106T104500Z;;;Test

DALARM:20081106T104500Z;;;Test

END:VEVENT

END:VCALENDAR



The event is from 11:00-12:00 UTC, which would be 12:00-13:00 
GMT+1/Berlin. This doesn't match either the event time on your PDA, 
nor in Horde.

And how did you set up Kronolith? To store events in UTC or in the 
local timezone?
11/06/2008 08:38:22 AM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
Please read http://wiki.horde.org/SyncMLProblemReport and follow the 
steps to generate complete SyncML debugging information.
11/06/2008 05:24:18 AM Chuck Hagenbuch Assigned to Jan Schneider
Assigned to Karsten Fourmont
State ⇒ Assigned
 
11/02/2008 12:48:56 AM stefan (at) pluecken (dot) de Comment #1
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ Synchronization
Summary ⇒ Timezone problem on sync with synthesis
Type ⇒ Bug
Priority ⇒ 2. Medium
Reply to this comment
I just installed the synthesis demo version on a windows mobile 6.1 
PDA trying to sync with horde. When I try to sync with kronolith the 
times of the appointments are wrong by one hour.



Some background info:

- The timezone on the PDA is set to "GMT+1 Berlin,Rom"

- The timezone on the server is set to "Europe/Berlin"

- The timezone in the horde options (under "Locale and Time") is set 
to "Europe/Berlin"



Bug occurs when:

- I add an appointment on the PDA from 10:00-11:00, sync it, it 
becomes 11:00-12:00 in Horde.

- I add an appointment in Horde from 10:00-11:00, sync it, it becomes 
09:00-10:00 on the PDA.



Horde is the snapshot from 
http://ftp.horde.org/pub/snaps/2008-11-01/horde-HEAD-2008-11-01.tar.gz 
and Kronolith same directory, same date: 
kronolith-HEAD-2008-11-01.tar.gz

Saved Queries