Bug 508689

Summary:	improper processing of multiple vevent per vcalendar
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Christof Schulze <christof.schulze>
Component:	DAV Resource	Assignee:	kdepim bugs <kdepim-bugs>
Status:	REPORTED ---
Severity:	normal	CC:	carl
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	working.ics as referenced in the description. This validates using https://icalendar.org/validator.html#l1 broken.ics as per description. This is wht is visible in akonadiconsole as RAW Payload

Description Christof Schulze 2025-08-24 23:18:03 UTC

Created attachment 184416 [details]
working.ics as referenced in the description. This validates using https://icalendar.org/validator.html#l1

SUMMARY


Akonadi-Konsole: 6.3.3 (24.12.3)
KDE Frameworks: 6.13.0
Qt: 6.8.2 wird verwendet und gebaut wurde mit 6.8.2
Debian GNU/Linux 13 (trixie) (Xcb)
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.12.38+deb13-amd64


STEPS TO REPRODUCE
1. use radicale to serve a calender that contains attached ics (working.ics)
2. subcribe to this collection using akonadi
3. observer broken.ics to be visible in akonadiconsole and as a result have incorrect recurrance for this appointment.




OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Christof Schulze 2025-08-24 23:19:05 UTC

Created attachment 184417 [details]
broken.ics as per description. This is wht is visible in akonadiconsole as RAW Payload

Comment 2 Christof Schulze 2025-08-25 06:43:35 UTC

I was struggling a bit with the form, therefore the report is a bit untidy. Is there a way I can edit? If not, should I send a different, cleaned-up version?

Comment 3 Christof Schulze 2025-08-27 13:08:20 UTC

the original vcalender contains multiple vevent entries, all with the same UUID and each of those referencing a different recurrence ID which then has deviating DTSTART and DTEND defined that describe the exception for this recurrence.
It seems, akonadi is not parsing that correctly.