Bug 307806

Summary: akonadi empties my groups/distribution lists regularly
Product: [Frameworks and Libraries] Akonadi Reporter: Anders Lund <anderslund>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: major    
Priority: NOR    
Version: 4.9   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Anders Lund 2012-10-04 06:16:55 UTC 
I have a setup where my addressbook is stored in owncloud, so that it can be shared between devices.

Unfortunately, this storage does not appear to support groups, so I created a "personal contacts" resource for this purpose.

Problem: my groups are so often emptied, in kaddressbook the page is blank, if I edit such a destroyed group, I see a list of "the contact does not exist any more". But IT DOES. All my people are in my addressbook, and listed just below in kaddressbook.

It looks to me like akonadi just drops and recreates these contacts every time they are synced, causing a new id to be assigned, breaking my groups.

Btw, I also think this adds to the insane CPU abuse akonadi causes by running nepomuk stuff ALL THE TIME.

There is a similar problem with the caldav calendars from owncloud, though less frustrating because no other data is destroyed in that case

Reproducible: Always
Comment 1 Anders Lund 2012-10-04 06:35:52 UTC 
I also wonder if there is a connection with the problems I have with address completion in kmail: If akonadi drops and recreates, and consequently reindexes, all my contacts all the time, it would be quite random if they are available for completion.
Comment 2 Denis Kurz 2016-09-24 20:39:29 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:12:55 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.