Writing to ics-files (for example: dismiss an event) forces an error in the ics file.
In my case, there's a file with 4781 lines. There are events that forces an alarm. After dismissing these alarms these events are written I'll get the following error-message by Sunbird:

[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [calIIcalProperty.value]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///D:/Programme/Mozilla.org/Sunbird/js/calItemBase.js :: anonymous :: line 625" data: no]

After deleting the following lines:
X-RAINLENDAR-LASTALARMACK;VALUE=DATE-TIME:20070116T090721Z

everything seems to be ok.

Is it possible to disable alarms in Rainlendar?

Bye
Duke

That's probably a bug in Sunbird. It should just ignore the items it doesn't recognize. Anyway, you can try to remove the alarm window from the skin and see what happens (hopefully it doesn't crash).

Yes, it seems to be a Sunbird bug. Sunbird will only crash, when a semicolon is used. After changing (manually) from ; to : between ACK and VALUE everything seems to be ok:
X-RAINLENDAR-LASTALARMACK:VALUE=DATE-TIME:20070119T080045Z

Removing the alarm window from the skin is what I hadn't seen.

Thanks
Duke

I've posted the bug and an exaple ics-file to bugzilla and I got the following information:
The rfc2445 grammar specifies that an x-property (s4.8.8.1) can only have an
x-name, and parameters must be xparams (s4.2) or they must be the LANGUAGE
parameter (s4.2.10).

x-prop = x-name *(";" xparam) [";" languageparam] ":" text CRLF

xparam = x-name "=" param-value *("," param-value)

x-name = "X-" [vendorid "-"] 1*(ALPHA / DIGIT / "-")

While I don't agree with rfc2445 that it should be necessary for x-property
parameters to be xparams, since that is how rfc2445 is specified, maybe
Rainlendar should use an x-name parameter name to be most compatible. For
example, use X-VALUE instead of VALUE. Is that accepted by Sunbird?

Duke

It seems to be an error of Rainlendar.

Comment #3:
1. Verified that changing VALUE to X-VALUE in the ics file prevents the
exception.

2. A recent revision of rfc2445 (dated just two days before this bug was filed)
permits an x-prop to contain a parameter, not just an xparam.

x-prop = x-name *(";" parameter) ":" text CRLF

tools.ietf.org/html/draft-ietf-calsify-rfc2445bis-04#section-3.8.8.1

So I'll confirm and change the summary
old: ics object with semicolon causes exception
new: ICS x-property should allow parameter, not just x-parameter (.value throws
exception)

Next step: Someone comfortable working on libical needs to find why this error
is thrown, maybe with a debugger. (Since it seems to be thrown by
calICalProperty.value, it is not thrown from the parser.)

Comment #4:
that update on a draft for a followup rfc still says that the value type is
text. So a value type of datetime is still not permitted.

True. I'll fix that.