Bug 293557 - akonadi deletes my contacts :-(
Summary: akonadi deletes my contacts :-(
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: VCard file resource (show other bugs)
Version: 1.0.0
Platform: Unlisted Binaries Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-07 18:32 UTC by Anders Lund
Modified: 2017-01-07 22:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Lund 2012-02-07 18:32:29 UTC 
Version:           1.0.0
OS:                Linux

After using the update function for an addressbook, akonadi simply destroyed most data in  a vcard file resource, located on my owncloud server. I have backup, but data was lost!

The few contacts that was kept was those that had been edited lately.

Reproducible: Didn't try


Actual Results:  
  

Expected Results:  
  

OS: Linux (i686) release 3.2.1-2-ARCH
Compiler: gcc
Comment 1 Anders Lund 2012-02-07 18:55:12 UTC 
I do NOT think it is good that akonadi deletes data without confirmation, given how unstable it is. Before data is deleted, the user should be asked in ALL cases.
Comment 2 Anders Lund 2012-02-07 18:58:37 UTC 
There is another possible explanation about how this happened, my netbook can have been without network during lot of time today. I believe this situation have lead to data loss before, akonadi thinking that remote files are empty when not connected. Maybe the connection were lost during its operation.
Comment 3 Denis Kurz 2016-09-24 20:41:58 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 4 Denis Kurz 2017-01-07 22:49: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.