Bug 183727 - It is not possible to delete expired appointments and completed todos.
Summary: It is not possible to delete expired appointments and completed todos.
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-08 21:53 UTC by Peter Gückel
Modified: 2010-03-03 01:21 UTC (History)
1 user (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 Peter Gückel 2009-02-08 21:53:32 UTC
Version:           4.2 rc1 (using KDE 4.2.0)
OS:                Linux
Installed from:    Fedora RPMs

[Curious - I have kde4.2.0 installed, but korganizer is still rc1.]

When deleting expired calendar entries and completed todos, they seem to be deleted, but when restarting korganizer, they are back! It is impossible to get rid of them. Even archiving the entries does not get rid of them (an archive is verily created, but upon restarting korganizer, the archived entries are still in the calendar).

I am able to edit entries, so, as a work-around, I have set repeating calendar entires to non-recurring, or changed the date to the distant past to get them not to show in the recent or upcoming weeks, but it is impossible to banish them fromthe calendar altogether.
Comment 1 Sergio Martins 2009-02-16 06:39:48 UTC
Are you using an akonadi resource?
Comment 2 Peter Gückel 2009-02-16 07:01:08 UTC
Yes, I have the akonadi addresses/birthdays and calendar correctly (I believe) set up.
Comment 3 Peter Gückel 2009-03-02 20:08:09 UTC
I have upgraded to kde-4.2.1 (yes, really!),, and akonadi does not work at all, so I have had to revert to using the old resources. I will try akonadi again, once it works on 4.2.1.
Comment 4 Sergio Martins 2009-03-14 00:29:07 UTC
Unable to delete was a known issue in resource local dir.

It was also a problem in ResourceAkonadi which is also fixed.

Why doesn't akonadi start? Do you want do debug this problem?

What does "akonadictl status" say?
Comment 5 Peter Gückel 2009-03-14 16:55:25 UTC
Akonadi was not operational until a couple of days ago. As I result, I reverted to the old resource files.

Nevertheless, I ran akonadictl status:

akonadictl status
Akonadi Control: stopped
Akonadi Server: stopped

I might set it up later today, if I have time and motivation. In the meantime, the resource files are working splendidly.
Comment 6 Sergio Martins 2010-03-03 01:21:11 UTC
(In reply to comment #5)

> I might set it up later today, if I have time and motivation. In the meantime,
> the resource files are working splendidly.

That was one year ago, closing then.