Akonadi/fr: Difference between revisions

From KDE UserBase Wiki
(Created page with "Au moment de l'écriture de ces lignes, les applications suivantes sont habilités à utiliser l'infrastructure '''Akonadi''' pour stocker et accéder aux données utilisateur d...")
(Created page with "Client de messagerie Utilise '''Akonadi''' pour stocker les courriers électroniques")
Line 10: Line 10:
:{|
:{|
{{AppItem|KMail|View-pim-mail.png|
{{AppItem|KMail|View-pim-mail.png|
KMail}}Mail Client
KMail}}Client de messagerie
Uses '''Akonadi''' to store emails
Utilise '''Akonadi''' pour stocker les courriers électroniques
|-
|-
{{AppItem|KAddressBook|View-pim-contacts.png|
{{AppItem|KAddressBook|View-pim-contacts.png|

Revision as of 20:24, 7 August 2011

Introduction

L'infrastructure Akonadi est chargé de fournir aux applications une base de données centralisée pour stocker, indexer et retrouver les informations personnelles de l'utilisateur. Cela inclut ses courriers, contacts, calendriers, événements, journaux, alarmes, notes, etc. Dans SC 4.4, KAddressBook est devenue la première application à démarrer en utilisant l'infrastructure Akonadi. Dans SC 4.7, KMail, KOrganizer, KJots, etc. ont été mis à jour pour utiliser également Akonadi. De plus, plusieurs composants graphiques Plasma utilisent aussi Akonadi pour stocker et retrouver des événements de calendrier, des notes, etc.

Au moment de l'écriture de ces lignes, les applications suivantes sont habilités à utiliser l'infrastructure Akonadi pour stocker et accéder aux données utilisateur de manière centralisée. Allez sur la page de chaque application pour en savoir plus.

KMail

Client de messagerie

Utilise Akonadi pour stocker les courriers électroniques

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.