Bug 346597

Summary:	trying to sync invalid ical
Product:	[Frameworks and Libraries] Akonadi	Reporter:	sedrubal <kde>
Component:	DAV Resource	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	critical	CC:	greg, kde
Priority:	NOR
Version:	1.13.0
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description sedrubal 2015-04-24 22:48:46 UTC

I'm trying to sync my CalDav Calendar with OwnCloud but it crashes all the time with an error 500 and OwnCloud is complaining: "The supplied iCalendar datetime value is incorrect: "

Reproducible: Always

Steps to Reproduce:
1. Add Dav-Ressource (OwnCloud (>5.0))
2. Edit local calendar entries
3. sync

Actual Results:  
Notification: 
 - "unable to retreive data: " and something about error 500
OwnCloud:
 - "The supplied iCalendar datetime value is incorrect: "
 - "Uninitialized string offset: 0 at <owncloud>/3rdparty/sabre/vobject/lib/Sabre/VObject/DateTimeParser.php#170 "


Expected Results:  
Sync is working fine

I'm not sure, which event brakes the sync. It might be an imported event, but if korganizer and akonadi can handle it, it might be good, if akonadi can convert it to a valid ical.

Comment 1 sedrubal 2015-04-25 00:49:33 UTC

The notification message says: "unable to retreive data: there was a problem with the request (500)"

Comment 2 Grégory Oestreicher 2015-08-19 21:34:57 UTC

Is this happening when creating an event or when trying to fetch them? If it's the latter then this may have been fixed. Can you confirm if you still have the issue?

Comment 3 sedrubal 2015-08-25 16:04:28 UTC

I think this was happening when akonadi tried to upload a local created event. Thank you

Comment 4 Denis Kurz 2017-06-23 20:16:55 UTC

This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 5 Denis Kurz 2018-02-01 09:47:08 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.