292173 - no error message when .ics is corrupted

Status: VERIFIED FIXED

(Calendar :: Internal Components, defect)

Description

[Jamie Zawinski]

My machine crashed, and I had some disk corruption -- one of my calendar files
was cut off in the middle of an entry and had ~24K of binary data tacked on just
after a "BEGIN VEVENT" line.

The result of this was that Sunbird silently ignored the entire calendar.  It
took me a couple days to notice that all of my events in that calendar had gone
away!

Fortunately I was able to reconstruct the file manually, but Sunbird should have
alerted me that the file was corrupted instead of silently ignoring it all.

Comment 1

[Joey Minta]

Jamie,
   This looks very close to the issue described in bug 278818, which was
reported first.  Please look over that bug and, if you agree that your report
describes the same issue, please resolve this bug as a duplicate of bug 278818.
 (You can also confirm that bug if you so choose, but generally the older bug is
given priority.)  

Comment 2

[Mike Shaver (:shaver emeritus)]

Agreed; I'll try to test this on the trunk and see if it's still there.

Comment 3

[Mike Shaver (:shaver emeritus)]

Unfortunately, I do not have cycles to work on Calendar stuff these days (just as it's getting to the good part!), so I am a bad owner for these bugs.  To delete the tragically-large chunk of bugspam, search for gregorianabdication.

Comment 4

[Joey Minta]

This was fixed by the error reporting mechanism that was introduced prior to the 0.3a1 release.

Comment 5

[Damian Szczepanik]

What is the expected behaviour when user tries to use corrupted file? when file is treated as corrupted? I tried to import something like this

BEGIN:
VERSIOVENT
END:VCALENDAR

and Sunbird does not warn me. I need this information to write good test case (or more if needed) for Litmus

Comment 6

[cmtalbert]

Damian, there should be a pop up error message if you encounter an invalid ICS.  If you don't encounter such a message, then that should be opened as a new bug (because this bug closed and verified a long time ago).