Bug 273505 - Infinite errors after removing a calendar
Summary: Infinite errors after removing a calendar
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 1.5.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-17 20:09 UTC by Aleix Pol
Modified: 2017-01-07 22:47 UTC (History)
2 users (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 Aleix Pol 2011-05-17 20:09:05 UTC 
Version:           4.6 pre (using KDE 4.6.2) 
OS:                Linux

I have a google calendar imported as CalDAV.
I wanted to removed, I right-clicked and selected "delete calendar folder".

I found out that I kept getting many "cannot remove file ." message boxes after triggering the deletion

(I solved it by killing korganizer and the message boxes)

Reproducible: Didn't try
Comment 1 Sergio Martins 2011-05-17 21:32:12 UTC 
The popup comes from the resource, not korg, reassigning.
Comment 2 Grégory Oestreicher 2011-05-19 22:33:35 UTC 
Hi,

The bug seems to come from Akonadi unfortunately, reassigning.

For the next ones to deal with this bug: when deleting a collection, itemRemoved() will be called on each item in the colletion. The DAV resource is using the parentCollection().remoteId(), that stores the calendar URL, to find the username to use. However parentCollection() seem invalid, or at least parentCollection().remoteId() is empty. Deleting individual items is working fine as parentCollection().remoteId() is correctly populated.

Cheers,
Grégory
Comment 3 Denis Kurz 2016-09-24 20:34:33 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:47:28 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.