Akonadi: Difference between revisions

From KDE Wiki Sandbox
m (→‎Introduction: changed title headings)
m (→‎Disabling the Akonadi subsystem: clarified the disabling section)
Line 58: Line 58:
{{Warning|1=Disabling the Akonadi subsystem causes all Akonadi-enabled applications to not have access to the user's data. This means you will not be able to use any of the above applications while Akonadi is turned off. If you understand this and still wish to disable the Akonadi subsystem, read on.}}
{{Warning|1=Disabling the Akonadi subsystem causes all Akonadi-enabled applications to not have access to the user's data. This means you will not be able to use any of the above applications while Akonadi is turned off. If you understand this and still wish to disable the Akonadi subsystem, read on.}}


The Akonadi server is launched automatically at login whenever any Akonadi-enabled application requests access to it.


Shut down the Akonadi server from the control module or the command line:
To disable the Akonadi subsystem, first, shut down the running Akonadi server from the control module or the command line:


{{Input|1=akonadictl stop}}
{{Input|1=akonadictl stop}}


Now, to disable autostarting the Akonadi server during login, edit the file <tt>~/.config/akonadi/akonadiserverrc</tt> and change <tt>StartServer</tt> from true to false:
Now, edit the file <tt>~/.config/akonadi/akonadiserverrc</tt> and change <tt>StartServer</tt> from true to false:


{{Output|1=StartServer=false}}
{{Output|1=StartServer=false}}


The Akonadi server will no longer launch automatically.
The Akonadi server should no longer launch automatically on login.


{{Note|1=The Akonadi server will still be started by any Akonadi-enabled application. Ensure that no akonadi-enabled application is launched or running. Remember to check Plasma widgets as well — the Digital Clock widget in the default panel, for instance uses Akonadi to optionally display Calendar events and this is enabled in its settings by default.}}
{{Note|1=The Akonadi server will still be started by any Akonadi-enabled application. Ensure that no akonadi-enabled application is launched at login or thereafter. Remember to check Plasma widgets as well — the Digital Clock widget in the default panel, for instance uses Akonadi to (optionally) display Calendar events and this is enabled in its settings by default.}}


==Frequently Asked Questions==
==Frequently Asked Questions==

Revision as of 18:34, 6 August 2011

Introduction

The Akonadi framework is responsible for providing applications with a centralized database to store, index and retrieve the user's personal information. This includes the user's emails, contacts, calendars, events, journals, alarms, notes, etc. In SC 4.4, KAddressBook became the first application to start using the Akonadi framework. In SC 4.7, KMail, KOrganizer, KJots, etc. were updated to use Akonadi as well. In addition, several Plasma widgets also use Akonadi to store and retrieve calendar events, notes, etc.

At the time of writing, the following applications are enabled to use the Akonadi framework to centrally store and access user data. Follow through to each application's page to learn more.

KMail
Mail Client

Uses Akonadi to store emails

KAddressBook
Contact Manager

Uses Akonadi to store contact information

KOrganizer
Personal Organizer

Uses Akonadi to store calendars, events, journals, etc.

KJots
Note Taking Application

Uses Akonadi to store notes

In addition to this, plasma widgets like the Digital Clock widget, the Notes widget also use Akonadi to store and retrieve events and notes.

Controlling the Akonadi server

The Akonadi control module in System Settings provides an easy means to starting, stopping, restarting and querying the status of the Akonadi server. You may also accomplish this from the commandline using the command akonadictl.

To start the Akonadi server,

akonadictl start

To stop the Akonadi server,

akonadictl stop

To restart a running Akonadi server,

akonadictl restart

To query the status of the Akonadi server,

akonadictl status

Disabling the Akonadi subsystem

Warning
Disabling the Akonadi subsystem causes all Akonadi-enabled applications to not have access to the user's data. This means you will not be able to use any of the above applications while Akonadi is turned off. If you understand this and still wish to disable the Akonadi subsystem, read on.


The Akonadi server is launched automatically at login whenever any Akonadi-enabled application requests access to it.

To disable the Akonadi subsystem, first, shut down the running Akonadi server from the control module or the command line:

akonadictl stop

Now, edit the file ~/.config/akonadi/akonadiserverrc and change StartServer from true to false:

StartServer=false

The Akonadi server should no longer launch automatically on login.

Note
The Akonadi server will still be started by any Akonadi-enabled application. Ensure that no akonadi-enabled application is launched at login or thereafter. Remember to check Plasma widgets as well — the Digital Clock widget in the default panel, for instance uses Akonadi to (optionally) display Calendar events and this is enabled in its settings by default.


Frequently Asked Questions

Refer to the Troubleshooting page for resolving glitches during migration. Akonadi's Glossary entry has a brief description of its purpose and other useful links. This page explains how Akonadi and KAddressBook work together.

If you are experiencing 100% CPU usage by the virtuoso-t process when using Akonadi and related applications, try this proposed workaround while it is being investigated: In KRunner's configuration page, disable the Nepomuk search plugin and the Contact plugin. Then, log out and back in. For further information and inputs, report back here or on the Forum or on the IRC channel #kontact.