Bug 337127

Summary:	Deleteing a iCal file resource spawns a lot of error messages
Product:	[Frameworks and Libraries] Akonadi	Reporter:	redcap <forenhampel>
Component:	ICal file resource	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	bberberov+kde
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
URL:	https://www.google.com/calendar/ical/berlin.vegan%40googlemail.com/public/basic.ics
Latest Commit:		Version Fixed In:

Description redcap 2014-07-05 22:04:58 UTC

I added an iCal file resource poiting to a remote file. After using it for some time, I tried to delete it. Deletion was successful, however, a lot a of error messages were spawned.

Reproducible: Always

Steps to Reproduce:
1. Create an iCal file resource using the above URL
2. open Korganizer and display calender item
3.Delete the iCal file resource
Actual Results:  
A lot of error messages are spawned, probably one for each calender item stating:

Error while trying to delete calendar item. Error was: No items found

Th resource gets deleted however

Expected Results:  
Delete the resource without spawning error messages

There are calendar files that do not cause tis behaviour on my machine, e.g.

http://www.kde.org/releaseschedule.ics

Comment 1 Boian Berberov 2015-06-30 18:20:07 UTC

I am experiencing the same error messages, but different circumstances.  Every time the remote calendar updates, the messages are generated (108 of them).  I tried using cron to download the calendar and just import it locally, but that did not solve it.  Now I have had to turn off "Enable File Monitoring" in the Calendar Properties and update the calendars manually with F5.

Comment 2 Denis Kurz 2016-09-24 20:36:06 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:36:01 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.