Revision history [back]

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple timed (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple timed (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple timed (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple timed (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

Some more information: This seems to be related to the timezone used on the device somehow. I am using Germany/Berlin usually ( which is at UTC+1 currently but will switch to +2 this weekend). If I switch the device to a timezone that doesn't have any DST and is constantly at UTC+2 it seems new events appear with the correct times.

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple timed (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

Some more information: This seems to be related to the timezone used on the device somehow. I am using Germany/Berlin usually ( which is at UTC+1 currently but will switch to +2 this weekend). If I switch the device to a timezone that doesn't have any DST and is constantly at UTC+2 it seems new events appear with the correct times.

EDIT (2014-11-10): This really seems to be related to DST, now that we switched to "winter time" recently, the times of my appointments appear to be correct in the calendar. Weird.

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple timed times (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

Some more information: This seems to be related to the timezone used on the device somehow. I am using Germany/Berlin usually ( which is at UTC+1 currently but will switch to +2 this weekend). If I switch the device to a timezone that doesn't have any DST and is constantly at UTC+2 it seems new events appear with the correct times.

EDIT (2014-11-10): This really seems to be related to DST, now that we switched to "winter time" recently, the times of my appointments appear to be correct in the calendar. Weird.

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple times (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

Some more information: This seems to be related to the timezone used on the device somehow. I am using Germany/Berlin usually ( which is at UTC+1 currently but will switch to +2 this weekend). If I switch the device to a timezone that doesn't have any DST and is constantly at UTC+2 it seems new events appear with the correct times.

EDIT (2014-11-10): This really seems to be related to DST, now that we switched to "winter time" recently, the times of my appointments appear to be correct in the calendar. Weird.

EDIT(2015-04-23): As others pointed out below, the issue is back since we changed back to DST in March.

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple times (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

Some more information: This seems to be related to the timezone used on the device somehow. I am using Germany/Berlin usually ( which is at UTC+1 currently but will switch to +2 this weekend). If I switch the device to a timezone that doesn't have any DST and is constantly at UTC+2 it seems new events appear with the correct times.

EDIT (2014-11-10): This really seems to be related to DST, now that we switched to "winter time" recently, the times of my appointments appear to be correct in the calendar. Weird.

EDIT(2015-04-23): As others pointed out below, the issue is back since we changed back to DST in March.

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple times (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

Some more information: This seems to be related to the timezone used on the device somehow. I am using Germany/Berlin usually ( which is at UTC+1 currently but will switch to +2 this weekend). If I switch the device to a timezone that doesn't have any DST and is constantly at UTC+2 it seems new events appear with the correct times.

EDIT (2014-11-10): This really seems to be related to DST, now that we switched to "winter time" recently, the times of my appointments appear to be correct in the calendar. Weird.

EDIT(2015-04-23): As others pointed out below, the issue is back since we changed back to DST in March.

UPDATE (2015-05-17): Still present with 1.1.4.29

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple times (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

Some more information: This seems to be related to the timezone used on the device somehow. I am using Germany/Berlin usually ( which is at UTC+1 currently but will switch to +2 this weekend). If I switch the device to a timezone that doesn't have any DST and is constantly at UTC+2 it seems new events appear with the correct times.

EDIT (2014-11-10): This really seems to be related to DST, now that we switched to "winter time" recently, the times of my appointments appear to be correct in the calendar. Weird.

EDIT(2015-04-23): As others pointed out below, the issue is back since we changed back to DST in March.

UPDATE (2015-05-17): Still present with 1.1.4.29

UPDATE (2015-06-16): Still present with 1.1.6.27

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple times (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

Some more information: This seems to be related to the timezone used on the device somehow. I am using Germany/Berlin usually ( which is at UTC+1 currently but will switch to +2 this weekend). If I switch the device to a timezone that doesn't have any DST and is constantly at UTC+2 it seems new events appear with the correct times.

EDIT (2014-11-10): This really seems to be related to DST, now that we switched to "winter time" recently, the times of my appointments appear to be correct in the calendar. Weird.

EDIT(2015-04-23): As others pointed out below, the issue is back since we changed back to DST in March.

UPDATE (2015-05-17): Still present with 1.1.4.29

UPDATE (2015-06-16): Still present with 1.1.6.27

UPDATE (2015-07-15): Still present with 1.1.7.24

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple times (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

Some more information: This seems to be related to the timezone used on the device somehow. I am using Germany/Berlin usually ( which is at UTC+1 currently but will switch to +2 this weekend). If I switch the device to a timezone that doesn't have any DST and is constantly at UTC+2 it seems new events appear with the correct times.

EDIT (2014-11-10): This really seems to be related to DST, now that we switched to "winter time" recently, the times of my appointments appear to be correct in the calendar. Weird.

EDIT(2015-04-23): As others pointed out below, the issue is back since we changed back to DST in March.

UPDATE (2015-05-17): Still present with 1.1.4.29

UPDATE (2015-06-16): Still present with 1.1.6.27

UPDATE (2015-07-15): Still present with 1.1.7.24

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple times (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

Some more information: This seems to be related to the timezone used on the device somehow. I am using Germany/Berlin usually ( which is at UTC+1 currently but will switch to +2 this weekend). If I switch the device to a timezone that doesn't have any DST and is constantly at UTC+2 it seems new events appear with the correct times.

EDIT (2014-11-10): This really seems to be related to DST, now that we switched to "winter time" recently, the times of my appointments appear to be correct in the calendar. Weird.

EDIT(2015-04-23): As others pointed out below, the issue is back since we changed back to DST in March.

UPDATE (2015-05-17): Still present with 1.1.4.29

UPDATE (2015-06-16): Still present with 1.1.6.27

UPDATE (2015-07-15): Still present with 1.1.7.24

UPDATE (2015-09-24): Seems to be fixed with 1.1.9.28!

After having updated to 1.1.0.38 all dates in my caldav synched calendars have shifted by one hour (everything is one hour later now). This seems to happen after the caldav sync runs for the first time after the upgrade. I have verified this multiple times (doing a factory reset in between and recreating the accounts) ... when still on 1.0.8.21 the times are correct and after the upgrade they're wrong.

This seems to only affect caldav synced calendars. BTW, there is a small difference between using the native buteo sync plugin and sync-evolution here. When using sync-evolution for caldav only new appointments synced in after the upgrade are affected.

BTW, I am using owncloud 7.0.2 on the server side.

Some more information: This seems to be related to the timezone used on the device somehow. I am using Germany/Berlin usually ( which is at UTC+1 currently but will switch to +2 this weekend). If I switch the device to a timezone that doesn't have any DST and is constantly at UTC+2 it seems new events appear with the correct times.

EDIT (2014-11-10): This really seems to be related to DST, now that we switched to "winter time" recently, the times of my appointments appear to be correct in the calendar. Weird.

EDIT(2015-04-23): As others pointed out below, the issue is back since we changed back to DST in March.

UPDATE (2015-05-17): Still present with 1.1.4.29

UPDATE (2015-06-16): Still present with 1.1.6.27

UPDATE (2015-07-15): Still present with 1.1.7.24

UPDATE (2015-09-24): Seems to be fixed with 1.1.9.28!

UPDATE (2015-10-23): Seems to be re-introduced in 2.0.0.10 Problem is not on Jolla side, see comment below -martinrusler