Closed
Bug 530944
Opened 15 years ago
Closed 15 years ago
Can't prepare calendar for use after upgrade to newest Shredder/Calendar nightly
Categories
(Calendar :: Provider: Local Storage, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 529853
People
(Reporter: bugzilla, Unassigned)
Details
Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.1.5) Gecko/20091123 Lightning/1.0pre Shredder/3.0.1pre I just upgraded to the newest version of Shredder and Calendar. After starting up Shredder I get the following error for all my local calendars: An error was encountered preparing the calendar located at moz-profile-calendar:// for use. It will not be available. (NS_ERROR_FAILURE) [mozIStorageStatement.reset]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///home/nachtarbeiter/.thunderbird/8rs3qzh5.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/modules/calStorageUpgrade.jsm :: ensureUpdatedTimezones :: line 419" data: no]
Comment 1•15 years ago
|
||
Probably the same as Bug 529853. Lightning builds with BuildID 2009112407xxxx or newer ought to contain the fix. What Lightning build did you used?
Reporter | ||
Comment 2•15 years ago
|
||
Sorry, I somehow forgot to include this. I'm using the 24-Nov-2009 04:08 PST build, which should the be latest nightly.
Comment 3•15 years ago
|
||
Patrick. please try the extension attached to the above mentioned bug.
Reporter | ||
Comment 4•15 years ago
|
||
Philipp, thanks. I just installed the extension. Unfortunately it doesn't help. After a restart I get (apart from the errors I described above): Your profile is: Not broken. I can then only click on continue. This happends both with the 24-Nov-2009 04:08 PST build and with the the 25-Nov-2009 05:35 PST build.
Reporter | ||
Comment 5•15 years ago
|
||
Version 0.2 of the extension fixed the issue. Thanks again for your work on this!
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Updated•15 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•