Summary: | CardDav data loss | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Stefan Kebekus <stefan.kebekus> |
Component: | DAV Resource | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | critical | CC: | greg, laidig |
Priority: | NOR | ||
Version: | 4.8 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | vcf to reproduce the bug |
Description
Stefan Kebekus
2012-08-06 07:42:45 UTC
Hi Do you still have this issue? I've tested right now with KDE 4.9.2 and Akonadi 1.8.0 and everything is working fine. Cheers, Grégory I can confirm this bug (or at least something very similar) with KDE 4.9.4. To reproduce this bug, try adding the attached .vcf as a VCF File address book and copy the contact to the ownCloud address book. The vcf contains a custom entry that contains an underscore which is not allowed in the vcf specification. Kontact seems to ignore this, ownCloud returns an error. After copying the contact to the ownCloud address book it is added to the cache and shows up just fine in KAddressBook for a while. There user does not get any error message at all and probably won't notice the loss of data until it's way too late... Akonadi Console shows: AgentBase(akonadi_davgroupware_resource_0): Unable to add item: There was a problem with the request. The item has not been created on the server. An unexpected error (415) occurred while attempting to upload https://[url]/apps/contacts/carddav.php/addressbooks/dani/archiv/uNQJBXZthD.vcf. (415). It's probably hard to prevent this error in all cases in the first place (and I've also been getting some strange 412 errors that I can't reproduce) but at least the error should be handled in a way that won't lead to unnoticed data loss. Created attachment 76321 [details]
vcf to reproduce the bug
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |