Since the time change on 31.03.2024, newly created appointments have the wrong time
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
People
(Reporter: linuxbox, Unassigned)
References
Details
Steps to reproduce:
- Create a new Thunderbird profile
- Start that profile
- Create a new CalDAV calendar
- Create an appointment at 8 pm
Actual results:
Since the time change on 31.03.2024(German Summer Time), newly created CalDAV appointments have the wrong time. For example, if an appointment is created at 8 pm, it is displayed in Thunderbird at 7 pm. Only after a restart of Thunderbird will this appointment be displayed correctly at 8 pm. The behavior is reproducible.
Expected results:
Appointments should be displayed immediately with the correct time and not only after a restart of Thunderbird
|
||
Comment 1•1 year ago
|
||
There's probably a mismatch of timezone set somewhere.
What timezone are you using set to use in Thunderbird? And is the server set to use something else (that didn't change at this time)?
|
Reporter | |
Comment 2•1 year ago
|
||
The time zone is the same on the server and client as Europe/Berlin.
If I use a different CalDAV client (Evolution), I do not have the error.
The error appears for the first time in Thunderbird 108. In Thunderbird 107.0b4 the error does not exist.
|
|
Reporter | |
Comment 3•1 year ago
|
||
Here a confirmation in an german thunderbird forum:
https://www.thunderbird-mail.de/forum/thread/94406-caldav-termine-um-2-stunden-verschoben/
|
||
Comment 4•1 year ago
|
||
I have the same problem. Tested with Thunderbird 115.10.1 (Windows 10 / Debian 12) and Kopano 8.7.25.0-2 on UCS-Server 5.0.7
Tests with Evolution or KDE KOrganizer to Kopano works fine.
Best regards
|
||
Comment 5•7 months ago
|
||
duplicate of bug 1797693?
|
|
Reporter | |
Comment 6•7 months ago
|
||
I cannot say whether it is a duplicate, as I interpret the bug report mentioned as meaning that the error only occurs on the day of the time changeover and only in one view. But I may be seeing this wrong.
In my report, however, I also tested the Thunderbird version in which the problem first occurred.
I don't think this is a duplicate of 1797693, because that bug:
(a) isn't specific to events synced over CalDAV
(b) persists after restarting Thunderbird.
Description
•