Bug 328201 - Akonadi control process not registered at D-Bus
Summary: Akonadi control process not registered at D-Bus
Status: RESOLVED DUPLICATE of bug 326480
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 1.10.3
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-29 11:07 UTC by Tsu Jan
Modified: 2013-11-29 14:01 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 Tsu Jan 2013-11-29 11:07:41 UTC
With every system start-up, Akonadi fails to work. The Akonadi Server Self-Test Report says:

Akonadi control process not registered at D-Bus

The problem can temporarily be fixed, at least, in two ways:

(1) Removing of  '~/.local/share/akonadi/db_data' and logging out and in; most of the time, Plasma crashes after log-in but Akonadi starts working;

(2) Using these commands:

pkill akonadi_control
pkill akonadiserver
akonadictl start

However, the problem appears again after a reboot.

Reproducible: Always




Notes:

(1) There's some info in this report for Ubuntu: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979
But I have Debian with the same issue.

(2) I haven't tried the second method yet but subscribers to the above report say that it works.

(3) I don't use (and don't have) Strigi. I need Akonadi just for Kmail and Korganizer.

(4) Some people have reported that removal of '~/.local/share/akonadi/' and '~/.config/akonadi/' has solved their problem but the problem returns with a system reboot, so it isn't related to corrupted database or wrong config. I even renamed '~/.kde' after that removal from outside KDE but the issue returned.

(5) I tried Akonadi-1.10.80 too and the problem persisted.
Comment 1 Tsu Jan 2013-11-29 14:01:06 UTC

*** This bug has been marked as a duplicate of bug 326480 ***