Bug 10218 - (int-169979) importing an ical file does not create any events on the newly created calendar
(int-169979)
: importing an ical file does not create any events on the newly created calendar
Status: NEW
Product: Calendar
General
: 5.0/(3.2010.02-8)
: N900 Maemo
: Unspecified normal with 2 votes (vote)
: ---
Assigned To: unassigned
: calendar-general-bugs
:
:
:
:
  Show dependency tree
 
Reported: 2010-05-20 18:18 UTC by Jan Urbański
Modified: 2010-10-01 17:03 UTC (History)
2 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Jan Urbański (reporter) 2010-05-20 18:18:47 UTC
SOFTWARE VERSION:
3.2010.02-8.203.1

EXACT STEPS LEADING TO PROBLEM: 
1. Download http://www.pgcon.org/2010/schedule/schedule.en.ics
2. Copy the file to the device with scp as /home/user/MyDocs/schedule.en.ics
3. Start the File manager application
4. Navigate to the file
5. Click on it
6. A menu shows up saying "Adding 44 events" in the top left corner
7. Select "Create a new calendar"
8. Click "Save"
9. The calendar app appears, no error messages are shown
10. In the calendar app, select "Settings"
11. Then select "Edit calendars"
12. There is a "schedule" calendar available, and its description says "(Local,
0 events)"
13. The events from the imported ical file do not appear on the calendar

EXPECTED OUTCOME:
The newly created calendar is populated with the events defined in the ical
file

ACTUAL OUTCOME:
The newly created calendar is empty

REPRODUCIBILITY:
always

EXTRA SOFTWARE INSTALLED:
nothing relevant to ical, calendar, etc.

OTHER COMMENTS:

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3)
Gecko/20100401 Firefox/3.6.3
Comment 1 Andre Klapper maemo.org 2010-05-20 20:13:36 UTC
Thanks for reporting this!
I can confirm this in the internal version 2010.12-9 also when opening it
directly in Calendar app instead of saving it first.
Comment 2 gregor herrmann 2010-10-01 17:03:36 UTC
I stumbled over this bug yesterday when trying to import some hand-crafted .ics
files.

After some playing around I think I found the cause:
The import chokes if a VEVENT has DTSTART and DURATION set. It works perfectly
if I add DTEND to each VEVENT. [0] (With or without DURATION.)

IMO this is a violation of RFC 2445 [1] which says, in my understanding, that
both DURATION and DTEND are optional; 4.6.1 also explains when events without
those fields are supposed to end.

[0] In the example from this bug report:
perl -pe 's/^DTSTART;(.*)/DTSTART;$1\r\nDTEND;$1/g' schedule.en.ics >
schedule.end.ics
[1] http://www.faqs.org/rfcs/rfc2445.html