Startup errors in Akonadi

2handband · 06-12-2010, 08:55 PM

Okay, I've been fighting with this problem for two days; hope somebody can help:

When I log in I get the following error:

Code:

akonadi server process not registered at d-bus

Kind of a wierd error to have, considering that once I kill the error message Akonadi runs fine. Earlier today I installed KDE 4.4.4 from Alien Bob's package and now I have an error that says:

Code:

Could not access the outbox folder (Unknown error. (Unknown resource)).

...on top of the previous error. Once again, everything seems to work after I kill the error message. I have tried:

1) re-naming ~/.local/share/akonadi and allowing a new one to be created
2) copying /usr/share/akonadi/agents to /usr/local/share
3) modifying /usr/bin/startkde as follows:

Code:

# Make sure that D-Bus is running
if test -z "$XDG_DATA_DIRS"; then
    XDG_DATA_DIRS="`kde4-config --prefix`/share:/usr/share:/usr/local/share:/usr/share/akonadi"
    export XDG_DATA_DIRS
fi

Any ideas? The folks at the KDE forums have been less than helpful; I actually had an administrator tell me that since Akonadi runs fine after the message windows are closed I should just ignore it. But I don't really feel like having to close out the errors every friggin' time I log in... there's got to be a way to fix this.

Just as a point of clarification, I'm running 13.1 with KDE 4.4.4.

allend · 06-12-2010, 10:48 PM

It is a very bad idea to be logging in as root, but if you must,
http://www.linuxquestions.org/questi...2/#post3897904

2handband · 06-12-2010, 11:08 PM

This is a regular user login.

Cesare · 06-14-2010, 08:06 AM

I've encountered a similar problem on my system (Slack 13.1, pure 64-bit, KDE 4.4.3)... whenever I start KMail I get an error message telling me that Akonadi couldn't be started. However, despite the error message the Akonadi daemon is running then. Start KMail again, and this time it will work.

The problem fits exactly the description in KDE bug report Nr.236538 (https://bugs.kde.org/show_bug.cgi?id=236538). Unfortunately, the suggested fix didn't work for me. I fetched the diffs from KDE's websvn and rebuilt kdepimlibs, but the problem remains.

Still, the fix did seem to work for the submitter, so it's propably worth a try and I'm curious to hear if it works for you and KDE 4.4.4

pr_deltoid · 06-25-2010, 06:17 PM

I had this problem and read that it's MySQL that causes this. I read a tutorial on setting MySQL up securely, and it worked perfectly afterwards.