Event time changes to one hour later when syncing to Caldav

Question

4

Event time changes to one hour later when syncing to Caldav

asked 2017-10-21 14:18:17 +0200

TomC
1085 ●29 ●49 ●50

updated 2017-11-06 19:51:55 +0200

There are related threads to this problems, but the issue seems a bit unclear (claims that it has been solved etc.) so I'm posting a new thread.

Related threads:

together.jolla.com/question/72193/recurring-event-off-by-one-hour/

together.jolla.com/question/60486/all-dates-shifted-by-one-hour-in-calendar-after-updating-to-11038/

together.jolla.com/question/90725/bug-calendar-posteo-some-new-events-one-hour-late/

I am using the calendar on Jolla 1 (v. 2.1.2.3) and syncing through Caldav to the Horde/Kronolith calendar in my ISP webmail account. The problem is that when I create a new event on the phone, the event is changed to one hour later when synced through Caldav. If I edit the event to the correct time, it is changed again when synced. Only when I edit the event in the webmail application and sync back to the phone, the time stays correct.

From the related threads I got the impression that the problem could reside on the Caldav account side (in this case the Horde calendar) and is related to daylight saving time (DST). However, if there is this type of a problem, I think it should be possible for Sailfish to handle the issue.

Are there comments from Jolla on this issue?
Are there workarounds?

Update 29 october 2017: Today when the annual DST period is over, it seems like this is related to DST.

Just now, I created an event for 30/10 and the problem did not appear. I created the exact same event, but for 26/10 and the time was changed to one hour later after syncing, so it definitely seems to be DST related.

Update 6 November 2017: The problem exists also on Xperia X (2.1.3.5) with the same DST relation.

Another problem concerns the same Jolla 1 calendar: https://together.jolla.com/question/172859/duplicate-caldav-events-in-jolla-1-after-sync-to-xperia/

edit retag flag offensive close delete

Comments

1

reproducible even when you move an existing event manually in calendar

pawel ( 2017-10-22 19:36:08 +0200 )edit

Can you provide an example of ical data corresponding to the faulty event as sent from server? Maybe by doing a HTTP request to the id of the event from a web browser.

Damien Caliste ( 2017-10-29 19:22:35 +0200 )edit

See answer below.

TomC ( 2017-10-30 08:11:26 +0200 )edit

Yes, I thank you. I'll give look this week. Did you intent the same hour for the two example you gave ? Should it be starting at 20 or 21h ?

Damien Caliste ( 2017-10-30 10:03:08 +0200 )edit

I set the starting time for both events to 20:00. For 26/10, the time was changed to 21:00.

TomC ( 2017-10-30 10:42:25 +0200 )edit

reproducible even when you move an existing event manually in calendar
pawel ( 2017-10-22 19:36:08 +0200 )edit
Can you provide an example of ical data corresponding to the faulty event as sent from server? Maybe by doing a HTTP request to the id of the event from a web browser.
Damien Caliste ( 2017-10-29 19:22:35 +0200 )edit
Yes, I thank you. I'll give look this week. Did you intent the same hour for the two example you gave ? Should it be starting at 20 or 21h ?
Damien Caliste ( 2017-10-30 10:03:08 +0200 )edit
I set the starting time for both events to 20:00. For 26/10, the time was changed to 21:00.
TomC ( 2017-10-30 10:42:25 +0200 )edit

Answer 1

1

answered 2017-10-29 20:07:34 +0200

TomC
1085 ●29 ●49 ●50

I exported .ics files from the Horde/Kronolith webmail calendar for both events (DST and no DST), in case they may bring some light to the issue:

DST

BEGIN:VCALENDAR
VERSION:2.0
X-WR-CALNAME:---
PRODID:-//The Horde Project//Horde iCalendar Library//EN
BEGIN:VEVENT
DTSTART;TZID=Europe/Helsinki:20171026T210000
DTEND;TZID=Europe/Helsinki:20171026T220000
DTSTAMP:20171029T175506Z
UID:---
CREATED:20171029T175052Z
LAST-MODIFIED:20171029T175052Z
SUMMARY:Test event
CLASS:PUBLIC
STATUS:CONFIRMED
TRANSP:OPAQUE
END:VEVENT
BEGIN:VTIMEZONE
TZID:Europe/Helsinki
BEGIN:STANDARD
DTSTART:18780531T000000
TZOFFSETFROM:+0139
TZOFFSETTO:+0139
TZNAME:HMT
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
DTSTART:19420403T000000
TZNAME:EEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
DTSTART:19421004T010000
TZNAME:EE-T
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
DTSTART:19810329T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3;UNTIL=19820328T000000Z
TZNAME:EEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
DTSTART:19810927T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=9;UNTIL=19820926T010000Z
TZNAME:EE-T
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
DTSTART:19830925T010000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=9;UNTIL=19950923T220000Z
TZNAME:EE-T
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
DTSTART:19830327T010000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:EEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
DTSTART:19961027T010000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:EE-T
END:STANDARD
END:VTIMEZONE
END:VCALENDAR

No DST

BEGIN:VCALENDAR
VERSION:2.0
X-WR-CALNAME:---
PRODID:-//The Horde Project//Horde iCalendar Library//EN
BEGIN:VEVENT
DTSTART;TZID=Europe/Helsinki:20171030T200000
DTEND;TZID=Europe/Helsinki:20171030T210000
DTSTAMP:20171029T175143Z
UID:---
CREATED:20171029T174930Z
LAST-MODIFIED:20171029T174930Z
SUMMARY:Test event
CLASS:PUBLIC
STATUS:CONFIRMED
TRANSP:OPAQUE
END:VEVENT
BEGIN:VTIMEZONE
TZID:Europe/Helsinki
BEGIN:STANDARD
DTSTART:18780531T000000
TZOFFSETFROM:+0139
TZOFFSETTO:+0139
TZNAME:HMT
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
DTSTART:19420403T000000
TZNAME:EEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
DTSTART:19421004T010000
TZNAME:EE-T
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
DTSTART:19810329T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3;UNTIL=19820328T000000Z
TZNAME:EEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
DTSTART:19810927T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=9;UNTIL=19820926T010000Z
TZNAME:EE-T
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
DTSTART:19830925T010000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=9;UNTIL=19950923T220000Z
TZNAME:EE-T
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
DTSTART:19830327T010000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:EEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
DTSTART:19961027T010000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:EE-T
END:STANDARD
END:VTIMEZONE
END:VCALENDAR

edit flag offensive delete publish link

Comments

I have the same problem. I sync my calendar using Microsoft Exchange and my Outlook account.

I too think it is related to daylight saving as it seemed to start when our daylight saving time commenced a few weeks ago.

I must say it's very frustrating.

Does the patch mentioned on one of the other threads fix the problem?

AlanBreen ( 2017-11-07 12:01:22 +0200 )edit

I haven't tried any patches, so I don't know about that.

So you must be located on the southern hemisphere, when you say that the DST period started recently? For me, in Finland, the problem ended recently, when the DST period ended for last summer.

TomC ( 2017-11-07 15:48:41 +0200 )edit

Yes, located in the southern hemisphere.

This is a serious limitation. I'd think nearly every smart phone user would use the calendar for appointments. This bug makes the events function in the calendar useless when an event is entered prior to the DST change for an event occurring after the DST change.

If other OS's can manage it then it must be possible for Sailfish to be able to handle DST changes too.

AlanBreen ( 2017-11-29 11:12:28 +0200 )edit

Answer 2

0

answered 2017-11-29 11:25:25 +0200

AlanBreen

1684 ●46 ●65 ●89

Using the Warehouse app I have installed "python-pytz for Sailfish OS". This seems to have fixed the DST issue.

edit flag offensive delete publish link

Comments

Now this is interesting. While I am thorougly annoyed of yet another system component needing its own copy and format of the Olsen database, this would be an easy solution for us. @TomC can you confirm that this is a solution?

Maus ( 2017-11-29 11:33:43 +0200 )edit

Event time changes to one hour later when syncing to Caldav

Comments

2 Answers

Comments

Comments

Question tools

Stats

Related questions

Event time changes to one hour later when syncing to Caldav

Comments

2 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions