Bug 284899

Summary:	akonadi vcard resource is not trustfully keeping data
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Anders Lund <anderslund>
Component:	VCard file resource	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	major	CC:	dvratil
Priority:	NOR
Version:	1.0.0
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:

Description Anders Lund 2011-10-24 20:43:05 UTC

Version:           1.0.0
OS:                Linux

Adding contacts to a vcard file resource through adkonadi/kaddressbook is not safe. I just added some contacts, and after restarting the system, they were NOT saved. I added them again, but I feel REALLY bad about trusting it!

The file is saved in owncloud, and accessed via webdav.

I thought akonadi should keep the data and not remove it if the resource/file can not be written to.

Reproducible: Sometimes

Steps to Reproduce:
add some contact to addressbook, using a vcard file resource in a remote location, then reboot

Actual Results:  
new contacts lost

Expected Results:  
contacts kept

OS: Linux (i686) release 3.0-ARCH
Compiler: gcc

Comment 1 Anders Lund 2011-10-24 20:52:42 UTC

I just checked the file, and after typing in those contacts again (- their mobile phone numbers which I have now lost) they are in the file for now. Backup needed.

I think akonadi vcard resource is broken, I have had problems with it before. It feels like it does not check if it gets a http error message when trying to access the file for example. I remember sometimes all contacts was just deleted. This time lucklily just new ones were lost.

It may be that something in my KDE session was broken, or the network was not available when akonadi was trying to write back. But that should not cause data loss!

Do you think using a vcard directory is more safe?

Comment 2 Denis Kurz 2016-09-24 20:36:01 UTC

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.

Comment 3 Denis Kurz 2017-01-07 22:05:54 UTC

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.