Bug 323513 - Contacts resource (.vcf directory) synchronisation incomplete
Summary: Contacts resource (.vcf directory) synchronisation incomplete
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Contacts resource (show other bugs)
Version: 4.10
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-14 21:04 UTC by Volker Kuhlmann
Modified: 2017-01-07 22:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Volker Kuhlmann 2013-08-14 21:04:05 UTC
The akonadi contacts resource doesn't sync properly with on-disk vcard files. It notices new files and those that have gone absent, but does nothing about changed ones.
The only solution is to delete all ~/.local/share/contacts/*.vcf first, and then synchronise the resource.

Reproducible: Always

Steps to Reproduce:
1. rm ~/.local/share/contacts/*.vcf
2. qdbus org.freedesktop.Akonadi.Control /AgentManager org.freedesktop.Akonadi.AgentManager.agentInstanceSynchronize akonadi_contacts_resource_0
3. kaddressbookmigrator
4. qdbus org.freedesktop.Akonadi.Control /AgentManager org.freedesktop.Akonadi.AgentManager.agentInstanceSynchronize akonadi_contacts_resource_0

Actual Results:  
Changed contacts are never picked up. Added/deleted contacts may be picked up eventually.

Expected Results:  
After synchronisation, the address book content reflects the actual state of the on-disk resource (= directory full of vcard files).
Only steps 3 and 4 above should be necessary.

This is for loading address book data into KDE from scripts; whether to use kaddrbookmigrator or creating vcard files directly in the resource directory is beside the point. Unfortunately there appears to be no command line push/modify/delete of contacts.
Comment 1 Denis Kurz 2016-09-24 20:33:33 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 2 Denis Kurz 2017-01-07 22:44:21 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.