Bug 270077 - ~/.kde/share/apps/akonadi_ical_resource_X keeps growing
Summary: ~/.kde/share/apps/akonadi_ical_resource_X keeps growing
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: ICal file resource (show other bugs)
Version: 4.6
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 265190 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-04-04 14:31 UTC by Michael Schuerig
Modified: 2017-01-07 21:37 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Schuerig 2011-04-04 14:31:25 UTC 
Version:           4.6 (using KDE 4.6.1) 
OS:                Linux

I have an Akonadi resource for my calendarat ~/.kde/share/apps/korganizer/std.ics. My understanding is that this is the usual way, i.e., I didn't set it up like this with a particular purpose.

Apparently versions of this file are kept at ~/.kde/share/apps/akonadi_ical_resource_3 without any cleanup. When I noticed this folder, it had more than 50 copies of the file, the oldest being more than 6 months old.

If the original resource was stored remotely, there would be a point in keeping a locally cached copy, but as std.ics is local, there's no point in having multiple copies.

Reproducible: Always



Expected Results:  
Do away with the unnecessary copies altogether or at least keep their number in check.
Comment 1 Volker Krause 2012-03-11 16:59:09 UTC 
*** Bug 265190 has been marked as a duplicate of this bug. ***
Comment 2 Denis Kurz 2016-09-24 20:41:05 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 21:37:34 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.