Bug 295292

Summary:	Akonadi's Birthdays (& Anniversaries) Resource keeps deleted entries
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Borden <borden_c>
Component:	Birthdays Resource	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	dnt500, kdenis
Priority:	NOR
Version:	1.13.0
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:

Description Borden 2012-03-04 06:49:34 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Iceweasel/10.0.2
Build Identifier: Version 0.99; KDE Development Platform 4.6.5

This bug may have a similar cause to #266451.  I have deleted a number of address book contacts with birthday entries in them.  Somehow, the Akonadi Birthdays & Anniversaries resource continues to track the birthdays in spite of the fact that the underlying contact is no longer there.  I can verify that the contact is very much gone from KAddressBook and Akonadi's Contact resources by attempting to compose an e-mail to a deleted contact.  KMail does not suggest any contacts that I have deleted.

Reproducible: Always

Steps to Reproduce:
1. Enable the Birthdays & Anniversaries resource in Akonadi.
2. Create a contact in an Akonadi-tracked address book with a birthdate.
3. Delete the contact from the address book.
Actual Results:  
The deleted contact's birthday information remains in KOrganizer and I get a birthday reminder for that deleted contact.

Expected Results:  
The contact's birthday should not appear anywhere in KOrganizer or in the Akonadi Console.

Comment 1 Rawk 2013-07-31 06:14:49 UTC

I'm experiencing the same problem. I've added a CardDAV resource and deleted it later. The birthdays are still in the birthdays resource.

Comment 2 Denis Kurz 2016-09-24 20:43:01 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 Rawk 2016-09-27 06:01:04 UTC

It's not present for me, anymore.

Comment 4 Denis Kurz 2016-09-27 06:21:16 UTC

Rawk, thanks again :-)