Calendar exceptions related to timezones causing Thunderbird mail to be fully broken
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
People
(Reporter: KaiE, Unassigned)
Details
(Keywords: regression)
Use Thunderbird 102 beta.
Use parameter -P and create a fresh profile.
Add an imap email account.
You see the folder pane on the left.
Quit Thunderbird.
Start Thunderbird again with the same profile.
Bug: Empty window, no folder pane on the left is shown.
Reporter | ||
Comment 1•3 years ago
|
||
The issue is related to system timezone. I'm on Linux, and my /etc/timezone file is set to: CET
We fail in CalTimezoneService.jsm and calUtils.jsm - it says it uses a system determined timezone CET, but then it cannot find that zone (probably because zones.jsm doesn't have it), and then complains that zone is null Ical.jsm convertToZone, which causes several exceptions in our code.
I also found that it works fine in an older Thunderbird profile, which I see contains a non-default pref value calendar.timezone.local which is set to Europe/Berlin for me. I'm very certain that I have never manually set that pref value, because it is a separate profile in a VM that never has had any calendar set up.
In short:
Current calendar code doesn't work on fresh profiles if the system timezone is a value like CET which isn't found in the zones.jsm file
Some older calendar code most likely automatically set the calendar.timezone.local pref which hides the problem with existing profiles.
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Comment 2•3 years ago
|
||
Using TB 91 these steps still work (on the same system that has timezone CET), and I automatically get the calendar.timezone.local pref with the good value.
I'm guessing that in 102 the code that calls Services.prefs.setStringPref("calendar.timezone.local", ...) in CalTimezoneService.jsm is no longer reached - but it seems that code is necessary to setup a proper timezone environment for thunderbird.
Reporter | ||
Comment 3•3 years ago
|
||
Using config editor, manually adding a calendar.timezone.local string entry with value Europe/Berlin (and restarting) fixes that profile.
Comment 4•3 years ago
|
||
I think this is bug 1760805.
Reporter | ||
Comment 5•3 years ago
|
||
agreed, duplicate.
I'll leave this for Lasana and Sean to resolve as duplicate, because they aren't yet cc'ed on the other bug.
![]() |
||
Comment 6•3 years ago
|
||
I'm not familiar with this part of the code but Sean has been looking into timezone issues recently. If this is a duplicate, then let's close.
Description
•