When I log into my desktop I get the following Akonadi error:

akonadi server process not registered at d-bus

What does that mean, and what can I do about it? I'm running Slackware 13.1.

This likely means that Akonadi failed to start.

What is the output of "akonadictl status" in Konsole?

Code: Select all

bash-4.1$ akonadictl status
Akonadi Control: running
Akonadi Server: running
Akonadi Server Search Support: available (backend: Virtuoso)

That message can likely be safely ignored, as Akonadi appears to be taking a bit longer than expected to start.

bcooksley wrote:That message can likely be safely ignored, as Akonadi appears to be taking a bit longer than expected to start.

Yeah, everything seems to be working properly... but the error message is still something I have to kill at every bootup. Is there anything I can do about it?

Okay, this is getting even more interesting. I just upgraded to 4.4.4... and now on top of the errors I was already getting the KDE crash handler is coming up at login time and telling me it couldn't access the outbox folder... unknown resource. But after I close out the errors (I have to close the KDE crash handler two or three times) akonadi seems to be running.

As bcooksley hinted, it sounds as though you have processes trying to use akonadi before akonadi has finished initialising.

annew wrote:As bcooksley hinted, it sounds as though you have processes trying to use akonadi before akonadi has finished initialising.

I get that... but is there anything I can do about it?

Couldn't say without knowing what process is already running so that you could possibly delay its start. One thought, though, is that akonadictl says that it is using the virtuoso backend. IIRC, that was slow to start up, and the inclusion of soprano fixed that. bcooksley can probably confirm or deny that, but it may be worth installing soprano.

I just checked and soprano is in fact installed.

I would simply recommend avoiding having applications that use Akonadi run on startup.

I guess that'll have to be the answer for now... I really hope this is fixed in 4.5! thanks for the help.