Bug 318662 - AgentManager can't delete "ghost" agent
Summary: AgentManager can't delete "ghost" agent
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.10
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-21 10:52 UTC by Thomas Tanghus
Modified: 2017-01-07 22:19 UTC (History)
0 users

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 Thomas Tanghus 2013-04-21 10:52:35 UTC
When testing DAV resource with ownCloud I was left with a ghost entry of an agent. I had manually configured a CardDAV agent and after deleting it, it is still listed in Kontact Contacts and in the Browser tab of akonadiconsole. It isn't listed in the agent list.
In akonadiconsoles Browser tab the "Delete folder" entry in the context menu is grayed out, and when I select "Delete Address Book" From Kontact the following is displayed in .xsession-errors and nothing else happens:

void AgentManager::removeAgentInstance(const QString&) Agent instance with identifier "" does not exist

The Attributes tab of folder properties says:
ENTITYDISPLAY: ("OC Contacts" "folder-remote" "" ())
AccessRights: WCD

The Internals tab shows 
Identifier 76
Remote identifier akonadi_davgroupware_resource_74
Content types: inode/directory; text/directory

When selecting "Dump to XML..." and select a file name, the following is written:
"Cannot connect to agent instance with identifier 'akonadi_davgroupware_resource_74', error message: 'Could not get owner of name 'org.freedesktop.Akonadi.Resource.akonadi_davgroupware_resource_74': no such name'"


Reproducible: Didn't try

Actual Results:  
The agent can't be fully deleted

Expected Results:  
The AgentManager should remove all parts of the agent.

KDE 4.10.2
Comment 1 Denis Kurz 2016-09-24 20:35:22 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 2 Denis Kurz 2017-01-07 22:19:12 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.