maemo.org Bugzilla – Bug 8463
libcalendar produces AALARM properties containing unescaped CRLF which prevents OSX synchronisation
Last modified: 2010-03-15 20:51:26 UTC
You need to
before you can comment on or make changes to this bug.
EXACT STEPS LEADING TO PROBLEM:
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
1. Enter an event on the N900 with an alarm
2. Using iSync on OSX, sync with the N900
3. Examine iCal for your event
The event appears with alarm details
The event does not appear at all
EXTRA SOFTWARE INSTALLED:
iSync plugin from https://garage.maemo.org/projects/n900isyncplugin/ on the
Capturing the bluetooth packets emitted by the N900, the AALARM entry sent
Logging the sync process on the Mac side produces error messages such as this
FUNCTION: -[VCalParser parseData:]
Failed to parse vCal (1) near index 97: BEGIN:VEVENT
And the event is rejected. If the AALARM line is changed to look like
then it is parsed correctly and the event will appear in iCal with the correct
I have developed a simple patch for src/VCalConverter.cpp in
libcalendar-backend that fixes this problem and allows correct syncing with OSX
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_2; en-US)
AppleWebKit/532.5 (KHTML, like Gecko) Chrome/220.127.116.11 Safari/532.5
Created an attachment (id=2114) [details]
Bluetooth activity log
Packet log captured by "PacketLogger" on OSX. The packet at 19:32:18.762
exhibits the extra 0x0D/0x0A characters in the AALARM: line
Details of the discussion of this issue can be found on talk.maemo.org at
Created an attachment (id=2115) [details]
Patch to VCalConverter.cpp
This patch is mainly code lifted from ICalConverter.cpp. It isn't pretty, but
I wanted to change as little as possible so I didn't refactor it to share the
Thanks for the report, investigation, and patch!
The relevant part of the vcal (augmented as per RFC822) BNF:
aalarmparts = 0*3(strnosemi ";") strnosemi
strnosemi = *(*nonsemi ("\;" / "\" CRLF)) *nonsemi
nonsemi = <any non-control ASCII except ";">
only allows escaped CRLFs. Confirming.
Just for your information, currently Nokia does not officially support the
usage of the bluetooth connection. Work is progressing with USB from the sync
(In reply to comment #5)
> Just for your information, currently Nokia does not officially support the
> usage of the bluetooth connection.
Sure, but the bug here is in the VCal conversion. Whether the converted output
is then transmitted via bluetooth, saved to a file, etc isn't relevant.
This has been fixed in package
which is part of the internal build version
(Note: 2009/2010 is the year, and the number after is the week.)
A future public update released with the year/week later than this internal
build version will include the fix. (This is not always already the next public
Please verify that this new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
To answer popular followup questions:
* Nokia does not announce release dates of public updates in advance.
* There is currently no access to these internal, non-public build versions.
A Brainstorm proposal to change this exists at
Setting explicit PR1.2 milestone (so it's clearer in which public release the
fix will be available to users).
Sorry for the bugmail noise (you can filter on this message).