Bug 287857

Summary: Akonadi ignores changes to contacts' vCard files
Product: [Frameworks and Libraries] Akonadi Reporter: Ivan D Vasin <ivan>
Component: Contacts resourceAssignee: Tobias Koenig <tokoe>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: kdepim-bugs, vkrause
Priority: NOR    
Version: 1.6.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ivan D Vasin 2011-11-29 19:57:58 UTC
Version:           1.6.0 (using KDE 4.7.2) 
OS:                Linux

this is with Akonadi 1.6.2.

some changes to an address book are much easier to make using non-Akonadi tools.  this is especially true for batch edits, and more especially if there is custom logic involved in the edits.

however, if i make some changes to my contacts, Akonadi apparently ignores them.  my setup is as follows:

* a Personal Contacts resource sourced from ~/.local/share/contacts-work.
* a Personal Contacts resource sourced from ~/.local/share/contacts-personal.
* an Akonadi Google Contacts resource sourced from my Google account.

if i make changes to the vCard files in ~/.local/share/contacts-work, the changes do not show up in KAddressBook, even if i right-click the address book and choose "Update Address Book folder".  it seems to me that the latter action should pull in any changes that were made externally to the vCard files.

a workaround is to remove and recreate the corresponding Personal Contacts resource.

Reproducible: Always

Steps to Reproduce:
1. create a Personal Contacts resource.
2. add or import some contacts via KAddressBook.
3. make some changes to the *.vcf files in the resource's directory.
4. open KAddressBook.
5. right-click the address book created in step 1, then choose "Update Address Book folder".

Actual Results:  
the changes made in step 3 are not visible in KAddressBook.

Expected Results:  
the changes made in step 3 are visible in KAddressBook after step 5.  it would be even better if this was true after step 4.
Comment 1 Ivan D Vasin 2011-11-29 19:58:51 UTC
this may be related to bug 273818 or bug 284899.
Comment 2 Denis Kurz 2016-09-24 20:40:40 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:37:20 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.