Disable Akonadi in KDE SC 4.7
How to avoid the Akonadi PIM framework of KDE is a very frequently asked question. Akonadi is started when logging into a default KDE session – and includes a mysql server – this is a bit of a waste of system resources since (in my personal estimation) the majority of KDE users won’t use Akonadi for anything at all.
So here’s how to make Akonadi not start in KDE SC 4.7.
Step 1
Disable KRunner runners that will start Akonadi. Press Alt+F2, click on the “wrench”, uncheck “Calendar Events” and “Contacts” runners, click on “Apply”.
Step 2
Tell the digital clock not to display calendar events. Right click the digital clock (in your panel), Digital Clock Settings, Calendar, uncheck “Display Events”, click “Apply”.
Step 3
Don’t use applications that need/start Akonadi, such as Kontact/KMail/KOrganizer, Konversation and Kopete.
That’s it. Next time you boot Akonadi won’t start anymore – at least not until needed.
PS
Personally I’m a huge user of Akonadi and the applications mentioned above, so this post should not be seen as any kind of vendetta against Akonadi or KDEPIM developers or anyone else. The purpose is solely to help KDE users who – unlike me – don’t need Akonadi get a leaner and cleaner system.
[...] – and includes a mysql server – this is a bit of a waste of system resources … More: Disable Akonadi in KDE SC 4.7 « The Blog is Hot This entry was posted in Uncategorized and tagged akonadi, avoid-the-akonadi, kde, mysql-server, [...]
Not use kontact konversation kopete? Then i would as well throw out KDE if I would like to turn off akonadi. All said and done I think it’s a huge and unnecessarily hard dependency for KDE. You basically want a DE and get the largest part of PIM all for free. Why not work on a KDE that has a soft dependency on akonadi while still being able to use kontact and konversation and kopete…
Akonadi is a soft dependency at runtime, as it is only started on demand, i.e. when an application wants to interact with it.
When PIM data provides added value but is not crucial for the main functionality, e.g. the clock’s calendar, then it makes sense to have an option to do without these additional features (e.g. the clock’s calendar event integration)
Nice try but no cigar. It is not soft in terms of ‘not necessary to install’ without major function loss. I mean come on. KDE without kontact, kopete and konversation + restrictions on how things need to be configured… get real. Akonadi is a hard dep in this respect. No akonadi means severe loss of function.
It is easier to package as a base dependency, but nevertheless a soft dependency at runtime due to not running when not needed.
Making the use configurable for add-on functionality is one option, these apps could also check if it is running.
When it provides the core functionality, e.g. in Kontact, neither of these option would make sense, since the application would be totally useless (empty, no data to work on) without.
The whole point of this post is that:
Most KDE users, use either Thunderbird or web based solutions for mail and calendaring. And add a few people using text based clients or even Evolution.
I’m guessing at least 98% never use IRC. Those who do will often use Xchat or irssi or other clients.
I don’t know how many people use instant messaging. Maybe 20%? A substantial amount of those will use browser based stuff or pidgin or psi etc.
While it might seem inconceivable to you, for most regular users, not using kontact+kopete+konversation is completely normal.
I like the idea of Akonadi, but the current implementation is not very efficient. On my system, akonadi_mixedmaildir_resource is taking over 1GB of memory and opening my inbox (~10k mails) for the first time takes several seconds. Before Akonadi, Kontact with KMail+Akregator active took about 150MB of memory and displayed my inbox within a second.
[...] Schlander has put up a great post on how to disable Akonadi and I haven’t had any messages pop up after following the steps he [...]
Translated to Russian http://www.gentoo.ru/node/23678
You could simply change
StartServer=true to StartServer=False
in
~/.config/akonadi/akonadiserverrc
I notice on my system that In this case akonadi still tries to start itself several times during KDE startup until it reaches some number of tries or timeout. The result is a delay in KDE startup. You _need_ to configure Krunner and clock as shown in this post to prevent Akonadi from starting.
[...] and Kopete installed: I can't remember why I stopped using Pidgin; but in a desperate attempt to get away from the whole Akonadi/Nepomuk mess, I stopped Kopete and searched for an alternative, which I found [...]