Bug 228726 - Recursive duplication of backup copy upon synchronisation
Summary: Recursive duplication of backup copy upon synchronisation
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: VCard file resource (show other bugs)
Version: 4.4
Platform: Ubuntu Unspecified
: NOR normal
Target Milestone: ---
Assignee: Volker Krause
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-02-27 11:46 UTC by Stéphane Magnenat
Modified: 2018-10-21 05:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stéphane Magnenat 2010-02-27 11:46:23 UTC
Version:            (using KDE 4.4.0)
Installed from:    Ubuntu Packages

I'm storing my contacts inside a vcard file through Akonadi. As I have two computers (work and home), I'm synchronizing this file using unisson. Thus I have enabled file monitoring in the configuration of the vcard resource. In KDE 4.3, this works fine. In KDE 4.4, the vcard resource is creating a lot of VCARDFILE.vcard_X, with X growing fast. I'm using the same scheme for synchronizing the calender through a vcal file and it works fine, only a single backup is done.

Is the new behaviour a bug, or is it a design choice? If it is done on purpose, could you suggest me a work-around? Should I use the vcard dir?

Thank you, all the best!
Comment 1 Tobias Koenig 2010-08-02 21:00:59 UTC
Hej Stéphane,

where is the file you are talking about located? What Akonadi resources do you have configured to access the file?

Ciao,
Tobias
Comment 2 Andrew Crouthamel 2018-09-20 21:53:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-21 05:23:57 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!