Draciron Smith - 31.08.18, 18:41:
> I had the same issue. Akondi was clobbering my system and making it
> utterly unusable. It is a resource MONSTER. I wouldn't even consider
> running it without at least 16 gigs of ram and the way I multitask I
> doubt that's enough.
>
> I got it stopped, don't remember exactly what I did but I think I
> followed this
> https://userbase.kde.org/Akonadi#ApplicationTable
>
> ~/.config/akonadi/akonadiserverrc change StartServer=true to
> StartServer=false
>
> Should keep it from autostarting once you disable the Akondi enabled
> apps from kicking off.
That did not work here with ~/.config/akonadi/akonadiserverr as in:
[Debug]
Tracer=null
[%General]
Driver=QSQLITE
Startserver=false
[QSQLITE]
Name=/home/martin2/.local/share/akonadi/akonadi.db
On initial session startup after login in with the test user and empty
home directory Akonadi was not even started. That was when it would
still use MariaDB. However on second startup of the session with above
configuration file it was started immediately on session startup.
An easy way to disable Akonadi might be to move
/usr/share/dbus-1/services/org.freedesktop.Akonadi.Control.service
out of the way, or probably "akonadictl", or well whatever starts
Akonadi once a widget or applications accesses it and reboot. I do not
know for sure, as I never bothered with disabling Akonadi. But with some
trial and error this should be easy enough to find.
I do not know what would break… by doing so. I bet applications and
widget would not be able to access Akonadi anymore and complain in some
way or another.
Thanks,
--
Martin
