[Tickets #12843] Re: Wrong timezone calculation with CalDAV

[n***@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12843
------------------------------------------------------------------------------
Ticket | 12843
Updated By | Jan Schneider <***@horde.org>
Summary | Wrong timezone calculation with CalDAV
Queue | Kronolith
Version | 4.1.4
Type | Bug
-State | Unconfirmed
+State | Feedback
-Priority | 3. High
+Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


Jan Schneider <***@horde.org> (2013-11-18 21:15) wrote:

Which Android client do you use, and can you listen on the wire what
it sends, with wireshark or similar?

[n***@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12843
------------------------------------------------------------------------------
Ticket | 12843
Updated By | ***@deffayet.com
Summary | Wrong timezone calculation with CalDAV
Queue | Kronolith
Version | 4.1.4
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------

Post by n***@bugs.horde.org
Which Android client do you use, and can you listen on the wire what
it sends, with wireshark or similar?

I use Google Calendar on Samsung Galaxy Note 2 running 4.1.2 stock image.
Local time zone is GMT+1

I don't have any tools for listen what it send. The traffic is over HTTPS.

Is it possible to enable something on Horde side for log to a file
what Horde receive from Android device and what Horde do (timezone
calculation, etc...) ?

Did some settings can be set in PHP files for avoid to enable full
global verbose debug that generate a lot of data ?

Thanks

[n***@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12843
------------------------------------------------------------------------------
Ticket | 12843
Updated By | Jan Schneider <***@horde.org>
Summary | Wrong timezone calculation with CalDAV
Queue | Kronolith
Version | 4.1.4
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


Jan Schneider <***@horde.org> (2013-11-19 13:59) wrote:

The Google calendar doesn't have anything to do with CalDAV, let alone
Horde. There is no builtin CalDAV support in Android either. You must
be using a 3rd party application, if this is really about CalDAV
synchronization with Horde.

[n***@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12843
------------------------------------------------------------------------------
Ticket | 12843
Updated By | ***@deffayet.com
Summary | Wrong timezone calculation with CalDAV
Queue | Kronolith
Version | 4.1.4
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------

Post by n***@bugs.horde.org
The Google calendar doesn't have anything to do with CalDAV, let
alone Horde. There is no builtin CalDAV support in Android either.
You must be using a 3rd party application, if this is really about
CalDAV synchronization with Horde.

Hello,

I use caldav-sync from dmfs (http://dmfs.org/caldav/) for exchange
Caldav data between Google Calendar and Horde.

Please find bellow the capture of what caldav-sync sent to Horde
(event is scheduled for today from 18:00 CET to 19:00 CET):

--->
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//dmfs.org//mimedir.icalendar//EN
BEGIN:VTIMEZONE
TZID:Europe/Berlin
X-LIC-LOCATION:Europe/Berlin
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Europe/Berlin:20131119T180000
DESCRIPTION:Some Description
SUMMARY:CalDAV-Sync Test Event
LOCATION:Some Location
TRANSP:OPAQUE
STATUS:CONFIRMED
DTEND;TZID=Europe/Berlin:20131119T190000
LAST-MODIFIED:20131118T133721Z
DTSTAMP:20131118T133721Z
CREATED:20131118T133721Z
UID:d9efd40a-39b5-4d62-9129-83ff649fa1a8
BEGIN:VALARM
TRIGGER;VALUE=DURATION:-PT10M
ACTION:DISPLAY
DESCRIPTION:Default Event Notification
X-WR-ALARMUID:45da49a7-9941-4ff9-8b27-b45c5c4c4c39
END:VALARM
END:VEVENT
END:VCALENDAR
--->

Thanks

[n***@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12843
------------------------------------------------------------------------------
Ticket | 12843
Updated By | Jan Schneider <***@horde.org>
Summary | Wrong timezone calculation with CalDAV
Queue | Kronolith
Version | 4.1.4
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


Jan Schneider <***@horde.org> (2013-11-20 14:23) wrote:

Are you sure that the Note has the native Google Calendar app
installed? AFAIK all Samsung devices with Android 4.1 have Samsung's
S-Planner app instead.
Anyway, I tried both S-Planner on a Samsung device, and importing your
ics file directly. Both work perfectly fine with the correct time.

[n***@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12843
------------------------------------------------------------------------------
Ticket | 12843
Updated By | ***@deffayet.com
Summary | Wrong timezone calculation with CalDAV
Queue | Kronolith
Version | 4.1.4
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------

Post by n***@bugs.horde.org
Are you sure that the Note has the native Google Calendar app
installed? AFAIK all Samsung devices with Android 4.1 have Samsung's
S-Planner app instead.
Anyway, I tried both S-Planner on a Samsung device, and importing
your ics file directly. Both work perfectly fine with the correct
time.

Yes, i'm sure.

About Calendar
Version 201306302
(c)2013 Google Inc.

I don't use Samsung apps.

Thanks

[n***@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12843
------------------------------------------------------------------------------
Ticket | 12843
Updated By | ***@deffayet.com
Summary | Wrong timezone calculation with CalDAV
Queue | Kronolith
Version | 4.1.4
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------

Post by n***@bugs.horde.org
Are you sure that the Note has the native Google Calendar app
installed? AFAIK all Samsung devices with Android 4.1 have Samsung's
S-Planner app instead.
Anyway, I tried both S-Planner on a Samsung device, and importing
your ics file directly. Both work perfectly fine with the correct
time.

Problem seem to be located on Horde, i have tried to import the ICS
file provided in this ticket in Horde (thanks for the tips to test
this) and Horde show wrong time in Web Interface and show wrong time
in ICS exported from Web Interface.

If you try to import the ICS in Horde:

My Calendars [edit] -> Import
Import ICS file

You will see:

Event title: CalDAV-Sync Test Event
From 11/19/2013 17:00 to 11/19/2013 17:59 Timezone: Europe/Berlin

For reminder, the event is 18:00 CET to 19:00 CET.

Now, if we compare the ICS format of the this event:

Imported ICS file to Horde:
DTSTART;TZID=Europe/Berlin:20131119T180000
DTEND;TZID=Europe/Berlin:20131119T190000

Exported ICS file from Horde:
DTSTART:20131119T160000Z
DTEND:20131119T170000Z

This is wrong, as Horde should have & export:
DTSTART:20131119T170000Z
DTEND:20131119T180000Z

I have tested timezone convertion in php (DateTime/ DateTimeZone with
the exemple
http://stackoverflow.com/questions/2505681/timezone-conversion-in-php)
and this works file, so php is not faulty on Horde server.

Thanks

[n***@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12843
------------------------------------------------------------------------------
Ticket | 12843
Updated By | Jan Schneider <***@horde.org>
Summary | Wrong timezone calculation with CalDAV
Queue | Kronolith
Version | 4.1.4
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


Jan Schneider <***@horde.org> (2013-11-21 14:40) wrote:

Nevertheless, I cannot reproduce it. You need to track this down yourself.

[n***@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12843
------------------------------------------------------------------------------
Ticket | 12843
Updated By | ***@deffayet.com
Summary | Wrong timezone calculation with CalDAV
Queue | Kronolith
Version | 4.1.4
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------

Post by n***@bugs.horde.org
Nevertheless, I cannot reproduce it. You need to track this down yourself.

Did you have tried to import the ICS file bellow in Horde ?

--->
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//dmfs.org//mimedir.icalendar//EN
BEGIN:VTIMEZONE
TZID:Europe/Berlin
X-LIC-LOCATION:Europe/Berlin
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Europe/Berlin:20131119T180000
DESCRIPTION:Some Description
SUMMARY:CalDAV-Sync Test Event
LOCATION:Some Location
TRANSP:OPAQUE
STATUS:CONFIRMED
DTEND;TZID=Europe/Berlin:20131119T190000
LAST-MODIFIED:20131118T133721Z
DTSTAMP:20131118T133721Z
CREATED:20131118T133721Z
UID:d9efd40a-39b5-4d62-9129-83ff649fa1a8
BEGIN:VALARM
TRIGGER;VALUE=DURATION:-PT10M
ACTION:DISPLAY
DESCRIPTION:Default Event Notification
X-WR-ALARMUID:45da49a7-9941-4ff9-8b27-b45c5c4c4c39
END:VALARM
END:VEVENT
END:VCALENDAR
--->

My Calendars [edit] -> Import
Import ICS file


Did you see in the Web interface:

Event title: CalDAV-Sync Test Event
From 11/19/2013 17:00 to 11/19/2013 17:59 Timezone: Europe/Berlin

or

Event title: CalDAV-Sync Test Event
From 11/19/2013 18:00 to 11/19/2013 18:59 Timezone: Europe/Berlin

Thanks

[n***@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12843
------------------------------------------------------------------------------
Ticket | 12843
Updated By | Jan Schneider <***@horde.org>
Summary | Wrong timezone calculation with CalDAV
Queue | Kronolith
Version | 4.1.4
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


Jan Schneider <***@horde.org> (2013-11-22 14:04) wrote:

See comment 6

[n***@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12843
------------------------------------------------------------------------------
Ticket | 12843
Updated By | ***@deffayet.com
Summary | Wrong timezone calculation with CalDAV
Queue | Kronolith
Version | 4.1.4
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


***@deffayet.com (2013-11-22 19:11) wrote:

I'm sorry, there is really a problem as you can see bellow.
Can you please tell me how the timezone parsing is done in Horde when
importing ICS data ?

Did Horde use TZID and/or X-LIC-LOCATION line or use only DTSTART/DTEND ?

As you can see bellow, when timezone in TZID and X-LIC-LOCATION lines
are different than timezone in DTSTART and DTEND lines it works.

--->
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//dmfs.org//mimedir.icalendar//EN
BEGIN:VTIMEZONE
TZID:Europe/Berlin
X-LIC-LOCATION:Europe/Berlin
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Europe/Berlin:20131119T180000
DESCRIPTION:Some Description
SUMMARY:CalDAV-Sync Test Event
LOCATION:Some Location
TRANSP:OPAQUE
STATUS:CONFIRMED
DTEND;TZID=Europe/Berlin:20131119T190000
LAST-MODIFIED:20131118T133721Z
DTSTAMP:20131118T133721Z
CREATED:20131118T133721Z
UID:d9efd40a-39b5-4d62-9129-83ff649fa1a8
BEGIN:VALARM
TRIGGER;VALUE=DURATION:-PT10M
ACTION:DISPLAY
DESCRIPTION:Default Event Notification
X-WR-ALARMUID:45da49a7-9941-4ff9-8b27-b45c5c4c4c39
END:VALARM
END:VEVENT
END:VCALENDAR
--->

Show:

Event title: CalDAV-Sync Test Event
From 11/19/2013 17:00 to 11/19/2013 17:59 Timezone: Europe/Berlin
=> The date is converted but there is no reason to convert it as in
the ics file there is:
DTSTART;TZID=Europe/Berlin:20131119T180000
DTEND;TZID=Europe/Berlin:20131119T190000


Now, just do the following modification in the ICS file:
-DTSTART;TZID=Europe/Berlin:20131119T180000
+DTSTART;TZID=Europe/Paris:20131119T180000
-DTEND;TZID=Europe/Berlin:20131119T190000
+DTEND;TZID=Europe/Paris:20131119T190000

(and so keep Europe/Berlin for TZID and X-LIC-LOCATION.)

--->
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//dmfs.org//mimedir.icalendar//EN
BEGIN:VTIMEZONE
TZID:Europe/Berlin
X-LIC-LOCATION:Europe/Berlin
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Europe/Paris:20131119T180000
DESCRIPTION:Some Description
SUMMARY:CalDAV-Sync Test Event
LOCATION:Some Location
TRANSP:OPAQUE
STATUS:CONFIRMED
DTEND;TZID=Europe/Paris:20131119T190000
LAST-MODIFIED:20131118T133721Z
DTSTAMP:20131118T133721Z
CREATED:20131118T133721Z
UID:d9efd40a-39b5-4d62-9129-83ff649fa1a8
BEGIN:VALARM
TRIGGER;VALUE=DURATION:-PT10M
ACTION:DISPLAY
DESCRIPTION:Default Event Notification
X-WR-ALARMUID:45da49a7-9941-4ff9-8b27-b45c5c4c4c39
END:VALARM
END:VEVENT
END:VCALENDAR
--->

Show:

Event title: CalDAV-Sync Test Event
From 11/19/2013 18:00 to 11/19/2013 18:59 Timezone: Europe/Paris

Of course, i have tried this two imports tests multiple times for be
sure of the result.