Bug 297550 - It's impossible to remove a resource when the agent that created it is no more.
Summary: It's impossible to remove a resource when the agent that created it is no more.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.9
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-05 18:04 UTC by Alejandro Nova
Modified: 2017-01-07 21:26 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alejandro Nova 2012-04-05 18:04:16 UTC
Recently, I upgraded my Google Calendar resource, to solve sync problems. The Calendar resource was upgraded, but the Tasks resource was superceded by the new Tasks handling in the Calendar resource. And I was stuck with 2 Tasks resources: one, stuck in time, and the other, current.

When the Akonadi agent associated with the Tasks resource disappeared, Akonadi couldn't remove the resource anymore. I had to invalidate the resource using Akonadi Console, but Akonadi Console can't remove properly the resource, so I'm left with a ghost Tasks folder, that doesn't do anything.

Akonadi MUST gain the ability to remove resources on its own.
Comment 1 Frédéric COIFFIER 2012-08-20 15:28:22 UTC
I get the same problems with resources created by the external akonadi-google plugin which aren't reused by the resources created with the new kdepim 4.9.
Comment 2 Myriam Schweingruber 2012-08-22 06:39:57 UTC
Updating version and status.
Comment 3 Denis Kurz 2016-09-24 20:31:21 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 21:26:24 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.