Closed Bug 656312 Opened 13 years ago Closed 11 years ago

timezone not available in error console

Categories

(Calendar :: Calendar Frontend, defect)

Lightning 1.0b2
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: worcester12345, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.16 Safari/534.30
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18pre) Gecko/20110511 Lightning/1.0b2 Lanikai/3.1.11pre

Error: Assert failed: Timezone not available: GMT -0500 (Standard) / GMT -0400 (Daylight)
2: [file:///C:/Documents%20and%20Settings/xyzabc/Application%20Data/Thunderbird/Profiles/qrnynycg.abcxyz%2020041029/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/modules/calStorageHelpers.jsm:236] newDateTime
3: [file:///C:/Documents%20and%20Settings/xyzabc/Application%20Data/Thunderbird/Profiles/qrnynycg.abcxyz%2020041029/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/modules/calUtils.jsm -> file:///C:/Documents%20and%20Settings/xyzabc/Application%20Data/Thunderbird/Profiles/qrnynycg.abcxyz%2020041029/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calStorageCalendar.js:1331] cSC_getEventFromRow
4: [file:///C:/Documents%20and%20Settings/xyzabc/Application%20Data/Thunderbird/Profiles/qrnynycg.abcxyz%2020041029/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/modules/calUtils.jsm -> file:///C:/Documents%20and%20Settings/xyzabc/Application%20Data/Thunderbird/Profiles/qrnynycg.abcxyz%2020041029/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calStorageCalendar.js:759] cSC_getItems_
5: [file:///C:/Documents%20and%20Settings/xyzabc/Application%20Data/Thunderbird/Profiles/qrnynycg.abcxyz%2020041029/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/modules/calUtils.jsm -> file:///C:/Documents%20and%20Settings/xyzabc/Application%20Data/Thunderbird/Profiles/qrnynycg.abcxyz%2020041029/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calStorageCalendar.js:605] anonymous

Source File: file:///C:/Documents%20and%20Settings/xyzabc/Application%20Data/Thunderbird/Profiles/qrnynycg.abcxyz%2020041029/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/modules/calUtils.jsm -> file:///C:/Documents%20and%20Settings/xyzabc/Application%20Data/Thunderbird/Profiles/qrnynycg.abcxyz%2020041029/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calUtils.js
Line: 975

Reproducible: Always

Steps to Reproduce:
1. view error console
2. observe error
3.

Actual Results:  
see error

Expected Results:  
no error

no additional information at this time
Version: unspecified → Lightning 1.0b2
This information message means that one of your event in one of your calendars references a timezone that is not supplied with the calendar. I suggest that you check and fix your calendars.

This is just information and not an error. I filed Bug 432719 to correct the logging.
Depends on: 432719
(In reply to comment #1)
> This information message means that one of your event in one of your
> calendars references a timezone that is not supplied with the calendar. I
> suggest that you check and fix your calendars.
> 
> This is just information and not an error. I filed Bug 432719 to correct the
> logging.

Is it the calendar which needs to be checked, or an event? It was unclear from your above statement. Happy 4th of July.
This is one or more events that are referencing a missing timezone. The timezone information itself is stored on the calendar though. If you edit the events that have the mentioned timezone and set a different one, then the message will go away.
Can someone confirm this bug?
Giving up on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Resolution: WONTFIX → INCOMPLETE
I don't know why this was changed to "INCOMPLETE".  There is a problem, brought on not by me, but by the calendar itself. It was not fixed, and does not look like it will be.
Resolution: INCOMPLETE → WONTFIX
You need to log in before you can comment on or make changes to this bug.