Indeed, this is an error in the memory calendar when used as the offline cache and has been broken since 1.0 and bug 380060. Normally you shouldn't run into this case though. Can it be that you have set the preference calendar.cache.type to memory? Setting back to the default ("storage") should work around the bug for now. This patch should fix it, I haven't tested though.
Assignee: nobody → philipp
Status: NEW → ASSIGNED
Attachment #663955 - Flags: review?(matthew.mecca)
Comment on attachment 663955 [details] [diff] [review] Fix - v1 r=mmecca
Attachment #663955 - Flags: review?(matthew.mecca) → review+
When I got to Tbird config editor and type "calendar.cache.type", nothing comes up, where do I go to check that preference?
Pushed to comm-central changeset 567a0c810399
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.0
Backported to releases/comm-aurora changeset bd445c8913dd
Target Milestone: 2.0 → 1.9
Backported to releases/comm-beta changeset f2ea5e2fa4f5
Target Milestone: 1.9 → 1.8
If that pref doesn't show up I really don't know why its happening to you. I hope this patch fixes it, otherwise we will have to dig a bit deeper. If you are comfortable modifying code, you could unpack your lightning.xpi, go into the calMemoryCalendar.js, and add: cal.ERROR(cal.STACK(10)); to modifyOfflineItem. Then repack, install that Lightning and paste the stack here.
You need to log in before you can comment on or make changes to this bug.