View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004877||SOGo||Backend Calendar||public||2019-11-13 10:42||2019-12-15 14:28|
|Platform||Linux Debian 9||OS||Linux||OS Version||Debian 9|
|Fixed in Version||4.2.0|
|Summary||0004877: Event created with the most recent thunderbird are shifted one hour earlier in the web access and on Smartphone Client (ASync)|
I am using the most recent version of TB 68.2.2 (64-bit) on Linux with integrated Lightning. I connect to SOGo server 4.1.1 using CalDAV.
The local timezone is Europe/Paris. The server is Europe/Paris.
The bug is the following: when I created an event at 3PM in TB, it will appears at 2PM on the server integrated web access.
I have a smartphone connected to the SOGo server with ActiveSync. The event created in TB will also appear one hour earlier (2PM). The smartphone is also Europe/Paris.
I assume there is some kind of bug in handling of timezone / daylight saving in the server.
|Steps To Reproduce|
I am ready to run any test / report any extra data to solve this.
This is critical for organizing ourselves in our company.
Note : I used another server SOGo 4.0.0 with the same clients and it works smoothly.
|Tags||No tags attached.|
I can't reproduce the issue.
When was the event created?
Was it a repetitive event?
Show your full list of installed SOGo/SOPE packages.
Thanks for your quick answer.
The bug can be triggered when the event, is, for example created today
As an example, I just created in TB an event at 2PM tomorrow.
Here is the dump of this event from the SOGo database:
It was not a repetitive event.
It appears starting at 1PM instead of 2PM on my Smartphone which is
My full package list is below:
And what is the value of the SOGoTimeZone parameter in your sogo.conf?
What is the value of the user's timezone parameter from the General preferences panel?
root@server:~# cat /etc/sogo/sogo.conf | grep SOGoTimeZone
and the user timezone is also Europe/Paris.
Please can you check this bug? I can supply new information if needed. Best regards.
This might be similar to what is described in bug 4894.
Please try the latest nightly build.
I installed the latest nightly build and I can confirm that the problem is solved with the nightly build (tested with sogo_126.96.36.19991215-1_amd64.deb etc ...).
This ticket can be CLOSED and marked as SOLVED.
|2019-11-13 10:42||pmb||New Issue|
|2019-11-13 14:41||ludovic||Note Added: 0013895|
|2019-11-13 17:21||pmb||Note Added: 0013899|
|2019-11-13 18:01||ludovic||Note Added: 0013900|
|2019-11-13 19:13||pmb||Note Added: 0013902|
|2019-11-18 14:28||pmb||Note Added: 0013913|
|2019-11-25 22:36||pmb||Note Added: 0013926|
|2019-12-06 21:28||tfu||Note Added: 0013957|
|2019-12-10 21:16||francis||Relationship added||related to 0004894|
|2019-12-10 21:17||francis||Note Added: 0013971|
|2019-12-15 10:27||pmb||Note Added: 0013979|
|2019-12-15 14:28||francis||Assigned To||=> francis|
|2019-12-15 14:28||francis||Status||new => resolved|
|2019-12-15 14:28||francis||Resolution||open => fixed|
|2019-12-15 14:28||francis||Fixed in Version||=> 4.2.0|