"Unknown timezones" error dialog shows after each reload

NEW
Unassigned

Status

Calendar
General
9 years ago
6 years ago

People

(Reporter: Fabien de Saint pern, Unassigned)

Tracking

(Depends on: 1 bug)

Details

Attachments

(1 attachment)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.1.2) Gecko/20090803 Fedora/3.5.2-2.fc11 Firefox/3.5.2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3

At every calendar refresh, i have the message :

"Timezone Errors
See Error Console: Unknown timezones are treated as the 'floating' local timezone."

Error Console, many many :

Erreur : Unknown timezone "ECT" in "[...]".  Treated as 'floating' local timezone instead: 26/09/2007 09:30
BEGIN:VCALENDAR

PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN

VERSION:2.0

BEGIN:VEVENT

DTSTAMP;TZID=ECT:20090903T094018

SUMMARY: [...]
RRULE:FREQ=DAILY;UNTIL=20070927T220000Z;INTERVAL=2

DTSTART;TZID=ECT:20070926T093000

DTEND;TZID=ECT:20070926T110000

DESCRIPTION: [...]
LOCATION:[...]
X-LIC-ERROR;X-LIC-ERRORTYPE=VALUE-PARSE-ERROR:No value for UID property. 

 Removing entire property:

END:VEVENT

END:VCALENDAR


All events/tasks are ok (only local timezone) : is it possible to disable the message ?


Reproducible: Always
(Reporter)

Updated

9 years ago
Summary: Unknown → Unknown timezones
> All events/tasks are ok (only local timezone) : is it possible to disable the
> message ?

At the moment this is not possible, but we could use Thunderbird's Activity Manager in the future to present error/warning message in a prominent but undisturbing way. Also see bug 472483 for further information and development.
Status: UNCONFIRMED → NEW
Component: Internal Components → General
Depends on: 472483
Ever confirmed: true
OS: Linux → All
QA Contact: base → general
Hardware: x86 → All
Summary: Unknown timezones → "Unknown timezones" error dialog shows after each reload

Comment 2

7 years ago
I am experiencing this problem with Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11 connecting to a Microsoft Exchange server via EWS with DavMail 3.9.3-1750.  The problem doesn't occur when DavMail connects to the Exchange server via WebDAV/OWA instead.

Comment 3

7 years ago
Problem also occurs on Thunderbird 6.0.2 with Lightning 1.0b5.

Comment 4

6 years ago
Created attachment 622522 [details]
This notification gets shown every sync

every time my 30Boxes.com calendar is synced this notification displays, is there still no about:config setting to at least disable the notifications?
No longer depends on: 472483
Blocks: 472483
No longer blocks: 472483
Depends on: 472483

Comment 5

6 years ago
Here's an example of one of the errors that floods my console as well:


Timestamp: 9/27/2012 12:33:25 PM
Error: Unknown timezone "US/Eastern" in "Invite from Sherry: PXY Strong Museum".  Treated as 'floating' local timezone instead: Wednesday, April 15, 2009 1:00 PM
BEGIN:VCALENDAR
PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN
VERSION:2.0
BEGIN:VEVENT
DTSTAMP:20120927T123329
UID:X-30Boxes-67202674
SUMMARY:Invite from Sherry: PXY Strong Museum
DTSTART;TZID=US/Eastern:20090415T130000
DTEND;TZID=US/Eastern:20090415T130000
X-LIC-ERROR;X-LIC-ERRORTYPE=VALUE-PARSE-ERROR:No value for LOCATION proper
 ty. Removing entire property:
URL:http://30boxes.com/index.php?action=highlightDate&date=2009-04-15
END:VEVENT
END:VCALENDAR


Unfortunately the longest period of time that I can sync this calendar is 60 minutes, so once an hour my system starts churning while Thunderbird's console floods with errors and it slowly displays an error message pop-up.

Thunderbird 15.0.1
Lightning 1.7
My timezone is set to: America/New York

In the ICS file, this event looks like this:
BEGIN:VCALENDAR
CALSCALE:GREGORIAN
METHOD:PUBLISH
PRODID:-//83 Degrees Inc//30 Boxes//EN

X-WR-CALNAME;VALUE=TEXT:Travis's 30 Boxes
VERSION:2.0

(...etc...)

BEGIN:VEVENT
SUMMARY:Invite from Sherry: PXY Strong Museum
DESCRIPTION:
LOCATION:
DTSTART;TZID=US/Eastern:20090415T130000
DTEND;TZID=US/Eastern:20090415T130000
DTSTAMP:20120927T125758
UID:X-30Boxes-67202674
URL:http://30boxes.com/index.php?action=highlightDate&date=2009-04-15
END:VEVENT

(...etc...)

END:VCALENDAR

Let me know if there's any other debugging info or anything that I can do to help!
There is nothing Lightning can do, the calendar is just invalid. Your calendar references a timezone "US/Eastern" but doesn't provide it's definition. You need to fix your calendar to provide the timezone definition for "US/Eastern". Another workaround might be to edit the event in Lightning and change the timezone to one of Lightnings built-in timezones. In this case Lightning will add its timezone definition to the calendar.

Comment 7

6 years ago
As a user, it would be at least useful if there was a way to turn those errors off. Since it defaults to my local settings anyways, it has no effect for me on the accuracy of the events that it imports from the iCal/CalDAV/ICS/webcal location. These events are from a url that I subscribe to, so it's read only and I can't edit its events. Even if I could edit, I'd imagine that they would be reset after the next time it was refreshed.

So what I'd like to see Thunderbird/Lightning do:

* either ignore these errors by default (make them warnings?) or provide an option to not display these errors (either globally or for a given calendar)
* or allow alternate iCal VTIMEZONE TZIDs to be entered into an about:config entry
* and/or at least provide an option beyond refreshing a calendar every 60 minutes (ideally just let me specify how many minutes, but maybe options like "Daily" or "Upon Application Launch" would be useful)

Let me know if I should file a separate bug for that last one. I'm just trying to think of things I could do to not have that distracting (and in this case, pointless) error displayed every hour.


Also, FWIW, I ran the ICS file through this validator and it passed validation:
http://severinghaus.org/projects/icv/?url=
"Congratulations; your calendar validated!"


I did some googling to see where "US/Eastern" may have come from...

I dug into the RFC2445 (http://tools.ietf.org/html/rfc2445) it mentions this:
        Note: This document does not define a naming convention for time
        zone identifiers. Implementers may want to use the naming
        conventions defined in existing time zone specifications such as
        the public-domain Olson database [TZ]. The specification of
        globally unique time zone identifiers is not addressed by this
        document and is left for future study.

With this footnote:
   [TZ]       Olson, A.D., et al, Time zone code and data,
              ftp://elsie.nci.nih.gov/pub/, updated periodically.

That ftp site appears to be down, but I believe I have found a mirror, and inside this file:
ftp://munnari.oz.au/pub/oldtz/tzdata93b.tar.Z

In northamerica (line # 108):
# Zone	NAME		GMTOFF	RULES/SAVE	FORMAT	[UNTIL]
Zone	US/Eastern	-5:00	US		E%sT
You could set the reload interval to 'manually' for this calendar.

Lightning uses the time zone database <https://www.iana.org/time-zones/>, previously known as Olson database. As defined in the database the timezones are named like <Country>/<City>. According to the current release the name "US/Eastern" was removed in 1993.

Comment 9

6 years ago
(In reply to Stefan Sitter from comment #8)
> You could set the reload interval to 'manually' for this calendar.

That's not a bad idea. I wonder if I could pass in some kind of command line params to refresh it, in a sense refereshing it every time I launch Thunderbird. I'll look into how the "Cache" behavior works and how long that works, maybe I can tweak that. Thanks.


> Lightning uses the time zone database <https://www.iana.org/time-zones/>,
> previously known as Olson database. As defined in the database the timezones
> are named like <Country>/<City>. According to the current release the name
> "US/Eastern" was removed in 1993.

Oh, good to know, thanks again.
You need to log in before you can comment on or make changes to this bug.