Bug in Calendar App: Alarm to Calendar entry correctly goes off but Calendar entry is not visible in the Calendar

REPRODUCIBILITY (% or how often): ??
BUILD ID = OS VERSION (Settings > About product): 4.4.0.58
HARDWARE (XA2, X10, X10 II, …): X10 II
UI LANGUAGE: German
REGRESSION: (compared to previous public release: Yes, No, ?): ??

DESCRIPTION:

I just was correctly remined on an upcoming event. However, the event is not visible in the Calendar

PRECONDITIONS:

I have synched my calendar by importing an .ics file. The event is a reoccurring event that was changed multiple times.

STEPS TO REPRODUCE:

EXPECTED RESULT:

Event should be visible in Calendar (and alarm should be triggered)

ACTUAL RESULT:

Only the alarm is triggered, implying that the import of the calendar entry half-way worked

ADDITIONAL INFORMATION:

The .ics file for the entry looks as follows:

BEGIN:VCALENDAR
X-LOTUS-CHARSET:UTF-8
VERSION:2.0
PRODID:-//Lotus Development Corporation//NONSGML Notes 9.0.1//EN_C
METHOD:PUBLISH
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:19501029T020000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19500326T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=“W. Europe Standard Time”:20220118T130000
DTEND;TZID=“W. Europe Standard Time”:20220118T140000
TRANSP:OPAQUE
RDATE;VALUE=PERIOD:20220118T120000Z/20220118T130000Z
,20220201T120000Z/20220201T130000Z,20220215T120000Z/20220215T130000Z
,20220301T120000Z/20220301T130000Z,20220315T120000Z/20220315T130000Z
,20220329T110000Z/20220329T120000Z,20220412T110000Z/20220412T120000Z
,20220426T110000Z/20220426T120000Z,20220510T110000Z/20220510T120000Z
,20220524T110000Z/20220524T120000Z,20220607T110000Z/20220607T120000Z
,20220621T110000Z/20220621T120000Z,20220705T110000Z/20220705T120000Z
LAST-MODIFIED:20220328T092219Z
DTSTAMP:20220104T124016Z
SEQUENCE:0
CLASS:PUBLIC
DESCRIPTION:XXX
SUMMARY:XXX
UID:536F63654C7387F9C12587C00044E3B8-Lotus_Notes_Generated
X-LOTUS-UPDATE-SEQ:1
X-LOTUS-UPDATE-WISL:$S:1;$L:1;$B:1;$R:1;$E:1;$W:1;$O:1;$M:1;RequiredAttendees:1;INetRequiredNames:1;AltRequiredNames:1;StorageRequiredNames:1;OptionalAttendees:1;INetOptionalNames:1;AltOptionalNames:1;StorageOptionalNames:1;ApptUNIDURL:1;STUnyteConferenceURL:1;STUnyteConferenceID:1;SametimeType:1;WhiteBoardContent:1;STRoomName:1
X-LOTUS-NOTESVERSION:2
X-LOTUS-NOTICETYPE:A
X-LOTUS-APPTTYPE:3
X-LOTUS-CHILD-UID:536F63654C7387F9C12587C00044E3B8
BEGIN:VALARM
ACTION:DISPLAY

Thanks for the report. May you check the ICS data you pasted ? It is not terminating with END:VCALENDAR.

Thank you Damien, you are right. I missed to copy the entire .ics file. Since it is rather long, I just send you a private message.

I’m proposing a fix with https://github.com/sailfishos/mkcal/pull/27

The issue comes from the fact that the event is defined with RDATE only, starting in January. The events are not showing in the calendar, because, the incidence is actually loaded only when swiping to January, and then the ranges for the other months are already flagged as loaded in nemo-qml-plugin-calendar, so the occurrences for these ranges are not recomputed (and thus not displayed). The alarms are set because the event actually exists in the database, but are not shown due to the bug.

2 Likes

Thanks for highlighting this issue @JoOppen, and for the nice fix @dcaliste. Since this is now merged, I’ve tagged this bug as fixed.

It should make it in to the next release (after 4.4.0).

1 Like

Great, thank you!

20

1 Like