This forum has been archived. All content is frozen. Please use KDE Discuss instead.

akonadi is not starting automatically on login

Tags: None
(comma "," separated)
User avatar
jithin1987
Registered Member
Posts
135
Karma
0
OS
Hi,
I notice that my akonadi server is not autostarting by default. I have to manually start it. But my nepomuk and strigi seems to work correctly. Is this fine or am I missing something ?


jithin1987, proud to be a member of KDE forums since 2008-Oct.
Daniel_Boff
Registered Member
Posts
82
Karma
0
same here. systemsettings/akonadi says couln't register control program by d-bus. but after running aconadi_control it runs.
User avatar
jithin1987
Registered Member
Posts
135
Karma
0
OS
This the detailed report I got
http://nopaste.com/p/aRJGpRjuJ


jithin1987, proud to be a member of KDE forums since 2008-Oct.
User avatar
jithin1987
Registered Member
Posts
135
Karma
0
OS
It seems that when its starting automatically it cant find the akonadi resources and when done manually it can. Though both times its searching the same place. /usr/share/akonadi/agents


jithin1987, proud to be a member of KDE forums since 2008-Oct.
User avatar
jithin1987
Registered Member
Posts
135
Karma
0
OS
Finally fixed the issue. I deleted .config/akonadi .local/share/akonadi and then restarted.
Once logged in run kres-migrator. That fixes the startup issues. Got this from a launchpad bug report.

But in akonadi logs I can still see mysql error
[ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist

Is this a problem?
user base http://userbase.kde.org/Akonadi#Table_. ... .27t_exist
has an entry for this error. But this solution is not working.


jithin1987, proud to be a member of KDE forums since 2008-Oct.
User avatar
anda_skoa
KDE Developer
Posts
783
Karma
4
OS
Just to clarify this a bit:
Akonadi is currently not autostarted at all, just on demand (when an application using Akonadi requests it to be started).

The initial error had something to do with the MySQL database, not sure what went wrong exactly since it seemed to start and the shut down again.

Anything else later on is then a consequence of that.

As long as this new error doesn't make it fail its startup it is probably OK. Maybe it is something that would be probelmatic when being used as a central database (system daemon) when it has to check which user is allowed to perform which kind of access.

Cheers,
_


anda_skoa, proud to be a member of KDE forums since 2008-Oct.
User avatar
jithin1987
Registered Member
Posts
135
Karma
0
OS
One more doubt some times I see old akonadi error logs in self test report.
it says that "contol process died committing suicide."
sometimes it says " d-bus no longer running stuff"
I guess this happens during shutdown.
Is there any way to enforce that akondai quits before b-bus


jithin1987, proud to be a member of KDE forums since 2008-Oct.
User avatar
anda_skoa
KDE Developer
Posts
783
Karma
4
OS
Good question, I'll try to find an answer.

Cheers,
_


anda_skoa, proud to be a member of KDE forums since 2008-Oct.


Bookmarks



Who is online

Registered users: Bing [Bot], daret, Google [Bot], Sogou [Bot]