Open Bug 1294668 Opened 3 years ago Updated 3 years ago

"Could not extract integer from ":0"" {file: "resource://calendar/modules/ical.js" line: 103}

Categories

(Calendar :: General, defect, P3)

Lightning 5.3
defect

Tracking

(Not tracked)

People

(Reporter: jorgk-bmo, Unassigned)

Details

Attachments

(1 file)

Sorry, I'm not sure what to report here exactly.

I have a weekly reoccurring event, it alerted me this morning ("do market shopping") and I dismissed it.

Later I notice the attached message in the error console. Also the event was gone.

I switched from icaljs back to the C++ library and the event reappeared. When going back to icaljs it was also there.

Not so good if events get lost semi-silently.

The event is just this:

BEGIN:VEVENT
CREATED:20160724T110434Z
LAST-MODIFIED:20160812T111142Z
DTSTAMP:20160812T111142Z
UID:3daf8349-4abb-46a9-bbcb-a0356d18d82a
SUMMARY:Mercado Sant Pol
RRULE:FREQ=WEEKLY;UNTIL=20160930T080000Z
X-MOZ-LASTACK:20160812T111142Z
DTSTART;TZID=Europe/Berlin:20160729T100000
DTEND;TZID=Europe/Berlin:20160729T110000
TRANSP:OPAQUE
X-MOZ-GENERATION:8
X-MOZ-SNOOZE-TIME-1470988800000000:20160812T131142Z
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-PT15M
DESCRIPTION:Default Mozilla Description
END:VALARM
END:VEVENT

Oh, I just noticed: On export of the calendar there where more errors. So perhaps the database got corrupted?
Actually, I ran pragma integrity_check; using sqlite3.exe on Windows and it said: ok.
This is a known bug in the icaljs library, see bug 1179783. What version of Lightning do you use? The dependencies of bug 1179783 indicate that this might be fixed in Lightning 5.0.
I'm using Daily 51a1 with Lightning 5.3a1 to match. With dependencies you mean bug 1115667?
Version: unspecified → Lightning 5.3
Comment 2 is referring to the upstream pull request, which hasn't been yet been accepted (and therefore hasn't been included in the update from bug 1115667). This is also why bug 1179783 is not yet resolved completely.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.