GNU bug report logs - #79691
icedove: timezone parsing for Calendar broken

Previous Next

To reply to this bug, email your comments to 79691 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Isaac van Bakel <ivb <at> vanbakel.io>
To: bug-mumi <at> gnu.org
Subject: icedove: timezone parsing for Calendar broken
Date: Fri, 24 Oct 2025 18:09:35 +0200

I saw this reported in some IRC logs, but I couldn't find an issue for it.

With icedove <at> 140.3.0, the Calendar is completely unusable. This is 
apparently related to a failure to parse my system's timezone on 
startup, which appear in the error console like this:

    [JavaScript Error: "invalid line (no token ";" or ":") 
"Europe/Zurich[2025a]"" {file: 
"resource:///modules/calendar/Ical.sys.mjs" line: 1942}]'

The actual VTIMEZONE record received by Icedove really does contain the 
line "Europe/Zurich[2025a]" without a separator. This doesn't seem to be 
compliant, from my reading of the spec, so I'm not sure where it comes from.

When trying to actually interact with the Calendar, I get another error, 
which is caused by the default timezone being null:

    Calendar: TypeError: can't access property "wrappedJSObject", val 
is null
        getInTimezone resource:///modules/CalDateTime.sys.mjs:133
        now resource:///modules/calendar/utils/calDateTimeUtils.sys.mjs:71
        ...

Presumably the two are linked: Icedove is failing to parse the timezone 
information, and so isn't initialising the default timezone. I also 
can't pick a timezone in the application settings, since the dropdown is 
empty - I'm guessing this is a related issue.

Isaac

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.