Closed Bug 306691 Opened 19 years ago Closed 19 years ago

JS error using a clean install of 20050831 build

Categories

(Calendar :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: lapsap7+mz, Assigned: mostafah)

Details

Using a clean install (ie deleting the whole previous Sunbird program directory
and my own Sunbird profile directory) for 2005.08.31 build, I've got the
following error messages in JS console:

Error: subject.getBoolPref is not a function
Source File: chrome://calendar/content/pref/rootCalendarPref.js
Line: 99

Error: mozStorage exception: createStatement failed, statement: 'SELECT version
FROM cal_calendar_schema_version LIMIT 1', error: 'no such table:
cal_calendar_schema_version'
Source File: file:///C:/PROGRA~1/MOZILL~1.2_/components/calStorageCalendar.js
Line: 127
I got the following similar error when I first started Sunbird and imported my .ics file (I'm not sure exactly at what point it happened):

Error: mozStorage exception: createStatement failed, statement: 'SELECT version FROM cal_calendar_schema_version LIMIT 1', error: 'no such table: cal_calendar_schema_version'
Source File: file:///C:/Program%20Files/sunbird/components/calStorageCalendar.js
Line: 128


Interestingly, when I clicked on the link to view the source file, I got the following 3 additional JS errors:

No chrome package registered for chrome://communicator/content/contentAreaUtils.js .

No chrome package registered for chrome://communicator/content/utilityOverlay.js .

Error: Components.classes['@mozilla.org/rdf/datasource;1?name=charset-menu'] has no properties
Source File: chrome://global/content/charsetOverlay.js
Line: 211
I'm seeing the base error from comment 2 on Mac OS X too

Hardware: all ;; OS: all
This is fixed now.  There was some work done on the preferences in another bug and dmose restructured the storage calendar init so that it doesn't throw.  marking WFM.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.