Akonadi: Difference between revisions
(Marked this version for translation) |
|||
Line 23: | Line 23: | ||
For help getting address books recognised, please see [[Special:myLanguage/KAddressBook_4.4|KAddressBook]]. | For help getting address books recognised, please see [[Special:myLanguage/KAddressBook_4.4|KAddressBook]]. | ||
<!--T:10--> | |||
If you are experiencing 100% CPU usage, you should try this proposed workaround while it is being investigated. In KRunner's configuration page: | If you are experiencing 100% CPU usage, you should try this proposed workaround while it is being investigated. In KRunner's configuration page: | ||
<!--T:11--> | |||
Disable the Nepomuk search plugin. It is suspected that this is the cause of the problem. Please report back, here, on the Forum, or on IRC #kde-www if you try it. | Disable the Nepomuk search plugin. It is suspected that this is the cause of the problem. Please report back, here, on the Forum, or on IRC #kde-www if you try it. | ||
Revision as of 15:01, 3 January 2011
Introduction
In KDE Software Compilation 4.4 KAddressBook became the first application to use Akonadi. There are inevitable glitches in early stages of migration, and the Troubleshooting page will help solve them. For a brief description of the purpose of Akonadi, see this Glossary entry. You will also find useful links to further reading. Once the inevitable teething troubles are over Akonadi will provide a power-house usable by many applications.
The page KAddressBook will help you get your new-style address book working smoothly with KMail.
Understanding the Structure
You can, of course, simply use Kontact to manage all your address book, but if you have a backup system in place, for instance, you'll want to know where your data is, and how it's handled. The page Akonadi and AddressBook will help.
Troubleshooting Tips and Common Problems
If you have any problems with getting Akonadi working please visit the Troubleshooting page.
For help getting address books recognised, please see KAddressBook.
If you are experiencing 100% CPU usage, you should try this proposed workaround while it is being investigated. In KRunner's configuration page:
Disable the Nepomuk search plugin. It is suspected that this is the cause of the problem. Please report back, here, on the Forum, or on IRC #kde-www if you try it.