This page is mainly concerned with troubleshooting Akonadi, as there are inevitable glitches in early stages of migration. For many people the first signs of Akonadi activity will be in KDE SC 4.4, and many will be confused by it. For a brief description of the purpose of Akonadi, see '''[[Glossary#Akonadi|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.
Deze pagina gaat voornamelijk over het oplossen van problemen met '''Akonadi'''. Storingen zijn onvermijdelijk in de vroege stadia van de migratie.
Veel mensen zijn de eerste tekenen van'''Akonadi''' in '''KDE 4.4 SC''' en het zal velen verwarren.
Voor een korte beschrijving van het doel van '''Akonadi''', zie de '''[[Glossary/nl#Akonadi|Woordenlijst]]'''.
Daar staan ook nuttige verwijzingen naar meer informatie.
Zodra de onvermijdelijke aanloopproblemen voorbij zijn, is '''Akonadi''' een power-house dat bruikbaar is voor vele toepassingen.
===Understanding the Structure===
===De structuur begrijpen===
You can, of course, simply use Kontact to manage all your addressbook, 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.
U kunt natuurlijk ook gewoon'''Kontact''' gebruiken om al uw adresboeken te beheren, maar als u een bijvoorbeeld back-upsysteem hebt, wilt u weten waar uw gegevens zijn en daarmee wordt omgegaan. Dat staat beschreven op de pagina '''[[Akonadi_and_AddressBook/nl|Akonadi en AddressBook]]'''
== Troubleshooting Tips ==
== Tips voor het oplossen van problemen ==
* When reporting problems with the Akonadi server, always include the comprehensive self-test report. This report can be obtained from the self-test dialog which shows up whenever the Akonadi server was unable to start successfully. You can find the selftest dialog in the kcmmodule that is accessable via 'kcmshell4 kcm_akonadi'.
* Voeg bij het melden van problemen met de '''Akonadi'''server altijd het uitgebreide zelftestrapport toe.
U kunt dit rapport aanmaken dor het dialoogvenster zelftest dat automatisch wordt weergegeven als de '''Akonadi'''server niet kon opstarten.
De zelftest staat in de kcmmodule, die toegankelijk is via:
{{input|1=kcmshell4 kcm_akonadi}}
* Het handmatig starten van de '''Akonadi'''server vanaf de commandoregels kan ook bruikbare informatie opleveren. Start de server door in een console het volgende commando uit te voeren:
{{input|1=akonadictl start}}
Met deze opdracht kan de Akonadiserver weer gestopt worden:
{{input|1=akonadictl stop}}
Dit commando geeft meer nuttige informatie:
{{input|1=akonadictl status}}
== Veelvoorkomende problemen ==
* Starting the Akonadi server manually on the command line can result in additional useful information. This can be done by running '''akonadictl start''' on a console. Similar, with '''akonadictl stop''' the Akonadi server can be stopped again. '''akonadictl status''' gives more useful information.
=== Kontact start niet en geeft geen informatie ===
==Common Problems==
Als '''Kontact''' niet start, en u ziet geen foutmeldingen, controleer dan of '''Akonadi''' draait.
'''Akonadi''' moeten starten als daarom wordt gevraagd.
Als dat op uw systeem niet werkt, start het dan voordat '''Kontact''' opstart als u gemigreerde bronnen hebt; waarschijnlijk is dat '''KAddressBook'''.
Gebruik het icoon voor ''Akonadi'' in het systeemvak, dit wordt actief na het uitvoeren van "akonadi" in'''KRunner''', of typ de opdrachten in '''konsole''' om het te starten.
===Kontact doesn't start - and doesn't tell me anything===
=== Kontact start niet, versie II ===
If Kontact doesn't start, and you see no error messages, check that Akonadi is running. Akonadi should start on demand. If yours doesn't, you will have to start it before Kontact will start up if you have any migrated resources (most likely KAddressBook). Use the AkonadiTray icon (get this by typing 'akonadi' into KRunner) or type the commands into konsole to start it.
'''Kontact''' has been known to be hit after an update. If this happens, try starting '''KMail''', '''KOrganizer''' or any of the other applications from '''KRunner''' (or '''Konsole'''). Chances are high that they will work as stand-alone apps while you find what went wrong. This mainly affects version 4.4.0.
===Kontact doesn't start - version II===
===Map niet gevonden: "/Local"===
Kontact has been known to be hit after an update. If this happens, try starting KMail, KOrganizer or any of the other applications from KRunner (or Konsole). Chances are high that they will work as stand-alone apps while you find what went wrong. This mainly affects version 4.4.0.
Sommige gebruikers hebben deze foutmelding gemeld als '''Kontact''' niet wilde starten.
In een aantal vroege versies van 4.4 lijkt een bug te zitten in de migratie die '''KMail''' aangeeft om te kijken ~/.local/share/Local, een map die niet was aangemaakt.
De oplossing hiervoor is om niet te proberen dit probleem te verhelpen, maar terwijl '''KMail''' en/of ''' Kontact''' afgesloten zijn, de '''Akonadi Console''' te openen:
* Gebruik '''KRunner''', Alt-F2, of
* "akonadiconsole" '''konsole'''
===Folder not found: "/Local"===
Verwijder vervolgens de bron die aangeeft voor lokale e-mail te zijn.
Nu hoort '''Kontact''' of '''KMail''' te starten, en wordt de nieuwe bron aangemaakt met een verwijzing naar ~/.local/share/local-mail.
Some people have reported this error, when Kontact would not start. There seems to be a bug in the migration that is telling KMail to look for local mail in ~/.local/share/Local, a directory that had not been set up. The cure for this is not to attempt to correct it, but, with KMail/Kontact closed, to open the Akonadi Console (user krunner, Alt-F2, or 'akonadiconsole' in konsole), and remove the resource that it says is for local mail. You should now find that you can start Kontact or KMail, and that a new resource will be created, pointing to ~/.local/share/local-mail
===Er staan andere nieuwe mappen in ~/.local/share/===
===There are other new folders under ~/.local/share/===
Ja. Als uw adresboek correct is gemigreerd, wordt een nieuwe bron aangemaakt als ~/.local/share/contacts/.
Yes. If your addressbook has migrated correctly a new resource will have been created as ~/.local/share/contacts/
===Wat zijn /usr/bin/akonadi_maildir_resource en /usr/bin/akonadi_maildispatcher_agent?===
===What are /usr/bin/akonadi_maildir_resource and /usr/bin/akonadi_maildispatcher_agent?===
The ''akonadi_maildir_resource'' is created automatically by the ''akonadi_maildispatcher_agent'', while the latter is always started together with the ''Akonadi server'' as it provides basic functionality (e.g. sending mail) that is used by all mail applications that are (and will be) based on '''Akonadi'''. So it is ok that these two are running, as a user you can simply ignore them.
This autogenerated akonadi_maildir_resource will always point to ~/.local/share/local-mail/ which is your "Local folders" account where your local folders and emails will be stored.
The akonadi_maildir_resource is created automatically by the akonadi_maildispatcher_agent, while the latter is always started together with the Akonadi server as it provides basic functionality (e.g. sending mail) that is used by all mail applications that are (and will be) based on Akonadi. So it is ok that these two are running, as a user you can simply ignore them.
E-mail wordt op dit moment in '''KDE SC 4.4''' nog niet gemigreerd.
This autogenerated akonadi_maildir_resource will always point to ~/.local/share/local-mail/ which is your 'Local folders' account where your local folders and emails will be stored.
At this point, in KDE SC 4.4, mail is not yet being migrated.
===Nepomuk Indexing Agents zijn uitgeschakeld===
===Nepomuk Indexing Agents have been Disabled===
'''Kontact''' werkt nu, maar u blijft de volgende melding zien:
Kontact is now working, but you keep seeing this notice:
[[image:NepomukError.png|418px|center]]
[[image:NepomukError.png|418px|center]]
The most common reason for this notice is that '''Nepomuk''' is simply disabled in '''System Settings'''. Please try enabling it in '''System Settings''' under <menuchoice>Advanced -> Desktop Search -> Basic Settings</menuchoice> by checking "Nepomuk Semantik Desktop" and clicking "Apply".
The most common reason for this notice is that Nepomuk is simply disabled in System Settings. Please try enabling it in System Settings under Advanced / Desktop Search / Basic Settings by checking "Nepomuk Semantik Desktop" and clicking Apply.
If this does not help (or if the option was already checked when you got the error) and if you have previously been using prereleases of '''KDE SC 4.4''', you may be affected by a change to the database layout (due to an upgrade of the '''Virtuoso''' database server from version 5 to version 6; production releases of '''KDE SC 4.4''' are expected to be shipped with '''Virtuoso''' version 6). The following commands should get it working again:
If this does not help (or if the option was already checked when you got the error) and if you have previously been using prereleases of KDE SC 4.4, you may be affected by a change to the database layout (due to an upgrade of the Virtuoso database server from version 5 to version 6; production releases of KDE SC 4.4 are expected to be shipped with Virtuoso version 6). The following commands should get it working again:
Note that the above commands will '''not''' enable Nepomuk permanently if it isn't already enabled, you have to use System Settings for that.
A running Nepomuk is necessary to have a working Akonadi, and thus a working Kontact. However, you can disable the Strigi file indexer, which is not needed for Kontact. Strigi file indexing is used for desktop searching only, which is unrelated to Kontact. Just make sure Nepomuk itself is running correctly for Kontact.
Note that the above commands will '''not''' enable '''Nepomuk''' permanently if it isn't already enabled, you have to use '''System Settings''' for that.
In Kontact, Nepomuk is used for many different things, ranging from displaying upcoming birthdays, over handling free/busy lists to showing a contact photo in the message viewer. If Nepomuk is not running, several different things in Kontact will cease to work. The notice is there to warn you about the reduced functionality. Enabling Nepomuk as described above fixes the problem.
A running '''Nepomuk''' is necessary to have a working '''Akonadi''', and thus a working '''Kontact'''. However, you can disable the '''Strigi''' file indexer, which is not needed for '''Kontact'''. '''Strigi''' file indexing is used for desktop searching only, which is unrelated to '''Kontact'''. Just make sure '''Nepomuk''' itself is running correctly for '''Kontact'''.
You can check if Nepomuk is correctly running by typing ''akonadictl status''.
In '''Kontact''', '''Nepomuk''' is used for many different things, ranging from displaying upcoming birthdays, over handling free/busy lists to showing a contact photo in the message viewer. If '''Nepomuk''' is not running, several different things in '''Kontact''' will cease to work. The notice is there to warn you about the reduced functionality. Enabling '''Nepomuk''' as described above fixes the problem.
===I want to use my current Address Book and Organizer - Can I?===
U kunt controleren of '''Nepomuk''' correct draait met dit commando:
{{input|1=akonadictl status}}
===Ik wil mijn huidige adresboek en agenda gebruiken. Kan dat?===
Yes. When you use the Akonadi Console to add a resource it allows you to choose as Standard Addressbook - point that to your std.vcf should work fine. Migration does not destroy your old addressbook. You can continue to use it, though you will lose any benefits that Akonadi can bring. Alternatively you can have both an Akonadi addressbook and your original one, for a time, if you feel safer that way.
Yes. When you use the ''Akonadi Console'' to add a resource it allows you to choose as ''Standard Addressbook'' - point that to your std.vcf should work fine. Migration does not destroy your old addressbook. You can continue to use it, though you will lose any benefits that '''Akonadi''' can bring. Alternatively you can have both an '''Akonadi''' addressbook and your original one, for a time, if you feel safer that way.
===I can't see any details in my Address Book===
=== Ik zie geen gegevens in mijn adresboek ===
At the moment, the cause of this is not identified, but the cure is simple. Close Kontact, and start KAddressBook as a stand-alone application. After you close it you will be able to use it within Kontact. It seems that something is not being triggered when Kontact launches, and I expect this to be identified and fixed soon. This seems to mainly affect version 4.4.0.
At the moment, the cause of this is not identified, but the cure is simple. Close '''Kontact''', and start '''KAddressBook''' as a stand-alone application. After you close it you will be able to use it within '''Kontact'''. It seems that something is not being triggered when '''Kontact''' launches, and I expect this to be identified and fixed soon. This seems to mainly affect version 4.4.0.
===My contacts don't show when I use the Select button in KMail===
===Mijn contacten worden niet weergegeven als ik op Selecteren klik in KMail===
Check System Settings > Advanced tab > KDE Resources. Make sure that your Akonadi controlled address book(s) are listed there - add them if necessary. At the same time, it's a good idea to make your main Akonadi addressbook, usually called Personal Contacts, is set to be the default. More details of how this can be found in [[KAddressBook_4.4#Setting_up_your_New_AddressBook|here]].
Check <menuchoice>System Settings -> Advanced tab -> KDE Resources</menuchoice>. Make sure that your '''Akonadi''' controlled address book(s) are listed there - add them if necessary. At the same time, it's a good idea to make your main '''Akonadi''' addressbook, usually called "Personal Contacts", is set to be the default. More details of how this can be found in [[Special:myLanguage/KAddressBook_4.4#Setting_up_your_New_AddressBook|here]].
===How do I get my Groupware addressbook back?===
===Hoe krijg ik mijn groupwareadresboek terug?===
Two solutions: using the old framework or the new one.
Twee oplossingen: met het oude framework of met het nieuwe.
Old framework: In akonadiconsole, add a "KDE Address Book (traditional)". The KDE Address Book means you can set up old kresources for Akonadi. In the configuration of "KDE Address Book (traditional)", you point it to an "IMAP over KMail" KResource and in KMail, the groupware options should be enabled. This should work for Kolab, eGroupware and similar addressbooks - you will need to check the options to make sure that the correct type is selected.
Old framework: In ''akonadiconsole'', add a "KDE Address Book (traditional)". The KDE Address Book means you can set up old kresources for '''Akonadi'''. In the configuration of "KDE Address Book (traditional)", you point it to an "IMAP over KMail" ''KResource'' and in '''KMail''', the groupware options should be enabled. This should work for '''Kolab''', '''eGroupware''' and similar addressbooks - you will need to check the options to make sure that the correct type is selected.
New framework (only tested with Kolab): In the Akonadi configuration module (run 'kcmshell4 kcm_akonadi' to see it), add an "IMAP E-Mail Server" resource, and set up your mail server name, username and password, then click Auto-Detect. Then add a Kolab resource. The next step is to wait for the imap resource to synchronize, this can take quite a long time. The status will appear in the Akonadi configuration module. If nothing happens, try restarting akonadiserver. After some time the Kolab addressbook(s) should appear in KAddressBook.
New framework (only tested with '''Kolab'''): In the '''Akonadi''' configuration module add an "IMAP E-Mail Server" resource, and set up your mail server name, username and password, then click '''Auto-Detect'''. Run this command to see it:
{{input|1=kcmshell4 kcm_akonadi}}
Then add a '''Kolab''' resource. The next step is to wait for the imap resource to synchronize, which can take quite a long time. The status will appear in the '''Akonadi''' configuration module. If nothing happens, try restarting '''akonadiserver'''. After some time the '''Kolab''' addressbook(s) should appear in '''KAddressBook'''.
<span id="You experience long delays when sending mail"></span>
===Er zijn lange vertragingen bij het verzenden van e-mail===
===You experience long delays when sending mail===
Dit gaat gepaard met het bevriezen van '''KMail''' totdat de e-mail daadwerkelijk is verzonden.
This is accompanied by KMail freezing until the mail is actually dispatched.
A bug has been found in the way '''Nepomuk''' checks addresses, which can cause huge delays. This is fixed for SC 4.4.1. If you cannot get 4.4.1 yet, there is this work-around:
A bug has been found in the way Nepomuk checks addresses, which can cause huge delays. This is fixed for SC 4.4.1. If you cannot get 4.4.1 yet, there is this work-around:
Close '''Kontact''', or '''KMail''' and '''KAddressbook''' if you are running
stand-alone apps. Disable '''Strigi''' in '''SystemSettings'''. Stop '''Nepomuk''', delete the database and restart '''nepomukserver'''. The actual commands you need are (as user):
Close Kontact or KMail and KAddressbook if you are running
<!--T:42-->
stand-alone apps. Disable Strigi in SystemSettings. Stop Nepomuk, delete the
* '''20''' (formerly ''4''), '''disconnected'''. If you have access to the internet, your NetworkManager configuration must be wrong.
* '''70''' (formerly ''3''), '''connected'''. The problem must be somewhere else.
**It might be that one or more '''network interfaces''' are '''not controlled by NetworkManager'''. If that is your case, give the control of those interfaces to NetworkManager. It might be as simple as removing the entries for the interfaces from a text file (for example, <tt>/etc/network/interfaces</tt>). Check the help resources provided by your software distribution for more information.
=== Can't read any details of some messages or big delays to read it ===
if you aren't able to read some emails and see a message with " please wait ... ", you may logout and login KDE session to reinitialize all processes, might help.
==Een aantal technische kwesties==
=== Nepomuk ===
=== Nepomuk ===
Starting with KDE 4.4, it is required that Nepomuk is running in order for Akonadi to work correctly. Akonadi will check this and display an error dialog on startup if this is not the case.
Starting with KDE 4.4, it is required that '''Nepomuk''' is running in order for '''Akonadi''' to work correctly. '''Akonadi''' will check this and display an error dialog on startup if this is not the case.
Nepomuk only works with the Virtuoso backend.
'''Nepomuk''' only works with the '''Virtuoso''' backend.
You can check whether the Nepomuk is running with the correct backend by using the Akonadi self-test dialog, as described above.
You can check whether the '''Nepomuk''' is running with the correct backend by using the '''Akonadi''' self-test dialog, as described above.
Although Nepomuk is required to be running, you can still disable Strigi file indexing, which is usually the most resource-intensive part of the Nepomuk framework.
Although '''Nepomuk''' is required to be running, you can still disable '''Strigi''' file indexing, which is usually the most resource-intensive part of the '''Nepomuk''' framework.
=== Apparmor ===
=== Apparmor ===
Some distributions using Apparmor have it set up in a way that prevents Akonadi from running its internal database server. This can result in a variety of fuzzy error messages, including but not limited to the following:
Some distributions using '''Apparmor''' have it set up in a way that prevents '''Akonadi''' from running its internal database server. This can result in a variety of fuzzy error messages, including but not limited to the following:
* unknown error 255 when running akonadictl
{{output|1=unknown error 255 when running akonadictl
* "DB error: 'Could not open required defaults file: /home/$username/.local/share/akonadi/mysql.conf"
"DB error: 'Could not open required defaults file: /home/$username/.local/share/akonadi/mysql.conf"}}
You can solve this by running '''aa-complain mysqld''' with root privileges then reload apparmor.
You can solve this by running the following command with root privileges then reload apparmor:
On Kubuntu this is:
{{input|1=aa-complain mysqld}}
In ''Kubuntu'' is dit:
sudo aa-complain mysqld
{{input|1=sudo aa-complain mysqld
sudo /etc/init.d/apparmor reload
sudo /etc/init.d/apparmor reload}}
Note that you might be using Apparmor even if it does not show up in the process list.
Let op: wellicht gebruikt u '''Apparmor''' zonder dat dit zichtbaar is in de proceslijst.
Also note that some distributions ship an additional ''mysqld'' binary called ''mysqld-akonadi'' which has AppArmor set up correctly. If that's the case on your system and you see this problem nevertheless, there are two possible reasons:
Also note that some distributions ship an additional '''mysqld''' binary called '''mysqld-akonadi''' which has '''AppArmor''' set up correctly. If that's the case on your system and you see this problem nevertheless, there are two possible reasons:
* Akonadi still uses ''mysqld'' instead of ''mysqld-akonadi''. You can change that in Systemsettings -> Advanced -> Akonadi -> Server configuration.
* '''Akonadi''' still uses '''mysqld''' instead of '''mysqld-akonadi'''. You can change that in <menuchoice>Systemsettings -> Advanced -> Akonadi -> Server configuration</menuchoice>.
* AppArmor is not setup correctly for ''mysqld-akonadi'' either. Try running the ''aa-complain'' command noted above with ''mysqld-akonadi'' instead of ''mysqld''.
* '''AppArmor''' is not setup correctly for '''mysqld-akonadi''' either. Try running the "aa-complain" command noted above with '''mysqld-akonadi''' instead of '''mysqld'''.
<!--T:54-->
---
---
You will also experience this problem if you are running an encrypted home directory using encryptfs combined with AppArmor as the Akonadi apparmor profile currently does not account for an ecrypted home (common with Ubuntu Jaunty users). Error messages with include:
You will also experience this problem if you are running an encrypted home directory using encryptfs combined with '''AppArmor''' as the '''Akonadi apparmor''' profile currently does not account for an ecrypted home (common with ''Ubuntu Jaunty'' users). Error messages with include:
* dmesg produces:
* dmesg produces:
ecryptfs_do_create: Failure to create dentry in lower fs; rc = [-13]
{{output|1=ecryptfs_do_create: Failure to create dentry in lower fs; rc = [-13]
ecryptfs_create: Failed to create file inlower filesystem
ecryptfs_create: Failed to create file inlower filesystem}}
* Akonadi will list the following errors:
* Akonadi geeft de volgende foutmeldingen:
Akonadi server process not registered at D-Bus
{{output|1=Akonadi server process not registered at D-Bus}}
The fix is to edit the following file "/etc/apparmor.d/usr.sbin.mysqld-akonadi".
Dit is op te lossen door het bestand "/etc/apparmor.d/usr.sbin.mysqld-akonadi" aan te passen.
Below the line:
Voeg onder de regel:
@{HOME}/.local/share/akonadi/** rwk,
{{output|1=@{HOME}/.local/share/akonadi/** rwk,}}
Add a new line:
Voeg een nieuwe regel toe:
@{HOME}/.Private/** rwk,
{{input|1=@{HOME}/.Private/** rwk,}}
Restart apparmor and restart akonadi.
Herstart '''apparmor''' en herstart '''akonadi'''.
===Ontbrekende voorwaarde===
=== Missing Prerequisite ===
Om '''Akonadi''' te kunnen gebruiken, moeten de volgende packages geïnstalleerd zijn. Afhankelijk van uw distributie kunnen de namen anders zijn:
To use Akonadi you need to have the following packages installed (names might differ depending on your distribution):
* De ''MySQL server'' (die heet '''mysql''' in '''openSUSE''')
* Dee ''Qt4 MySQL plugin'' (die heet ''libqt4-sql-mysql'' in ''openSUSE'')
* The MySQL server (called ''mysql'' on openSUSE)
If you compile Qt4 yourself, make sure to tell the configure script to build in MySQL support by passing it the following option:
* The Qt4 MySQL plugin (called ''libqt4-sql-mysql'' on openSUSE)
{{input|1=-plugin-sql-mysql}}
If "configure" cannot locate the necessary MySQL client code (i.e, says "MySQL support cannot be enabled due to functionality tests") then ensure that the corresponding package is installed (typically called ''[lib]mysql[client]-dev[el]''). Also, depending on the install location of the MySQL headers, additional parameters to "configure" might be needed (eg. "-I /usr/include/mysql" on ''OpenSuse'').
If you compile Qt4 yourself, make sure to tell the ''configure'' script to build in MySQL support by passing it the '-plugin-sql-mysql' option. If ''configure'' cannot locate the necessary MySQL client code (i.e, says "MySQL support cannot be enabled due to functionality tests") then ensure that the corresponding package is installed (typically called ''[lib]mysql[client]-dev[el]''). Also, depending on the install location of the MySQL headers, additional parameters to ''configure'' might be needed (eg. ''-I /usr/include/mysql'' on OpenSuse).
Als u de Qt4 rechtstreeks van ''Nokia'' krijgt, zoals een download van <code>qt-sdk-linux-x86_64-opensource-2009.05.bin</code, dan krijgt u een foutmelding bij Test 1 tijdens het uitvoeren van het commando "akonadictl start":
If you get the Qt4 direct from Nokia, such as a download of
<!--T:99-->
qt-sdk-linux-x86_64-opensource-2009.05.bin
{{output|1=Database driver not found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration.
The following drivers are installed: QSQLITE.
Make sure the required driver is installed.}}
you will ( by the command "akonadictl start") get an error at Test 1:
U hebt de driver ''libqsqlmysql.so'' nodig.
''Database driver not found.''
''Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration.''
''The following drivers are installed: QSQLITE.''
''Make sure the required driver is installed.''
The driver you need is ''libqsqlmysql.so''
Helaas is deze driver is geen onderdeel van de distributie (tot januari 2010).
U moet de broncode compileren. Download dit bestand:
'''But''' the Revision '''4.6.1''', such as qt-sdk-linux-x86_64-opensource-2010.xx.bin
has the driver you needed.
=== Environment Setup ===
The '''Akonadi''' server searches for '''Akonadi''' agents and resources in the paths defined in the ''XDG_DATA_DIRS'' environment variable. If '''Akonadi''' complains about not finding agents or resources, check if this variable is set correctly. Also keep in mind that even if set in a current console session, it might not have been set when starting the server. Starting the server manually in the current console session excludes this cause.
The Akonadi server searches for Akonadi agents and resources in the paths defined in the '''XDG_DATA_DIRS''' environment variable. If Akonadi complains about not finding agents or resources, check if this variable is set correctly. Also keep in mind that even if set in a current console session, it might not have been set when starting the server. Starting the server manually in the current console session excludes this cause.
Als het logboek van de MySQL server de volgende foutmelding bevat, dan is uw MySQL server gebouwd zonder ondersteuning voor InnoDB, wat nodig is om gebruik te maken van '''Akonadi''', of '''InnoDB''' moet geladen worden in uw instellingenbestand ''mysql.conf'':
then your MySQL server was built without the InnoDB support which is required by Akonadi.
<!--T:100-->
{{input|1=#sql_mode=strict_trans_tables <- Add underneath this line
#plugins
plugin_dir=usr/lib/mysql/plugin < - This may be a different path
plugin-load=ha_innodb.so}}
===Table 'mysql. servers' doesn't exist===
Als het logboek van MySQL server de volgende foutmelding bevat, dan hebt u waarschijnlijk nog instellingenbestand voor MySQL:
===Table 'mysql. servers' doesn't exist===
<!--T:102-->
{{output|1=[ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
If MySQL server log contains the following error:
<code>[ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
[ERROR] Cannot open mysql.db
[ERROR] Cannot open mysql.db
[ERROR] Cannot open mysql.user
[ERROR] Cannot open mysql.user
[ERROR] Cannot open mysql.event</code>
[ERROR] Cannot open mysql.event}}
then, most probably, you don't have your MySQL configuration file in place. Copy it from ''/usr/share/config/akonadi/mysql-global.conf'' into ''~/.config/akonadi/mysql-local.conf''. (For debian and openSuSE users the file ist located in ''/etc/akonadi/mysql-global.conf''). Then open it and uncomment the line '''sql_mode=strict_trans_tables'''. If, after that, you get the following errors:
<code>[ERROR] Plugin 'InnoDB' init function returned error.
Copy it from ''/usr/share/config/akonadi/mysql-global.conf'' into ''~/.config/akonadi/mysql-local.conf''. (For ''debian'' and ''openSuSE'' users the file is located in ''/etc/akonadi/mysql-global.conf''). Then open it and uncomment the line '''sql_mode=strict_trans_tables'''. After that, you may get the following errors:
[ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE
failed.
<!--T:104-->
{{output|1=[ERROR] Plugin 'InnoDB' init function returned error.
[ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
[ERROR] Unknown/unsupported table type: innodb
[ERROR] Unknown/unsupported table type: innodb
[ERROR] Aborting</code>
[ERROR] Aborting}}
then in the same file find the line that starts just like the one above (which you have uncommented), but has additional parameters, separated by commas (something like '''sql_mode=strict_trans_tables,strict_all_tables, ...etc'''). Comment the shorter ''sql_mode=...'' line and uncomment the longer one.
If so, then in the same file find the line that starts just like the one above (which you have uncommented), but has additional parameters, separated by commas (something like '''sql_mode=strict_trans_tables,strict_all_tables, ...etc'''). Comment the shorter ''sql_mode=...'' line and uncomment the longer one.
On openSUSE 11.2 running the command
In ''openSUSE 11.2'' lost de volgende opdracht het probleem op:
This is a summary of other entries here for those upgrading from Kubuntu 9.10 to 10.4 who may have been using a personal package archive (PPA) for KDE 4.3 for bug fixes.
For ''Archlinux'':
Install missing prerequisites. Remove previous akonadi cache. Start the akonadi service. Install the database. Upgrade the database. Stop and restart the akonadi service.
This is a summary of other entries here for those upgrading from ''Kubuntu 9.10'' to 10.04 who may have been using a personal package archive (PPA) for KDE 4.3 for bug fixes.
|-
|akonadictl start
Install missing prerequisites. Remove previous '''akonadi''' cache. Start the '''akonadi''' service. Install the database. Upgrade the database. Stop and restart the '''akonadi''' service.
[http://forum.kde.org/viewtopic.php?f=20&t=79717 forum.kde.org Akonadi 1.2.1 - some issues]
[http://forum.kde.org/viewtopic.php?f=20&t=79717 forum.kde.org Akonadi 1.2.1 - een paar problemen]
=== KAddressBook upgrade ===
=== KAddressBook upgraden ===
In addition to the Kubuntu 10.4 remedy above, problems trying to add a Vcard directory may require
In addition to the ''Kubuntu 10.04'' remedy above, problems trying to add a ''Vcard directory'' may require the following command while '''Akonadi''' is not running:
If you get the following error when starting Akonadi:
Als u de volgende foutmelding krijgt bij het starten van Akonadi, dan gebruikt u waarschijnlijk een versie van MySQL server met een versie hoger dan 5.1.42:
<code>Character set 'latin1' is not a compiled character set and is not specified in
<!--T:84-->
the '/usr/share/mysql/charsets/Index.xml' file
{{output|1=Character set 'latin1' is not a compiled character set and is not specified in the '/usr/share/mysql/charsets/Index.xml' file
Nepomuk QueryServer interface not available!
Nepomuk QueryServer interface not available!
Connecting to deprecated signal
Connecting to deprecated signal
Line 280:
Line 322:
Last driver error: "QMYSQL: Unable to connect"
Last driver error: "QMYSQL: Unable to connect"
Last database error: "Can't initialize character set latin1 (path:
Last database error: "Can't initialize character set latin1 (path:
/usr/share/mysql/charsets/)"</code>
/usr/share/mysql/charsets/)"}}
then you're probably using a MySQL server which has a version > 5.1.42.
Er is een bekende regressie in MySQL 5.1.43 en 5.1.44 waardoor MySQL niet kan worden gestart.
There is a known regression in MySQL 5.1.43 and 5.1.44 which prevents MySQL from starting.
See [http://bugs.kde.org/226960 the bug report] for more details.
Zie de [http://bugs.kde.org/226960 bugmelding] voor meer details.
=== Restarting after a previous error ===
=== Herstarten na een eerdere fout ===
If you had problems starting Akonadi and fixed those (such as a missing package or the Apparmor problem) make sure that the Akonadi server is completely shut down before trying to start it again, by calling '''akonadictl stop''' on the command line. You can confirm that it was indeed shut down completely by running '''akonadictl status'''.
If you had problems starting '''Akonadi''' and fixed those (such as a missing package or the '''Apparmor''' problem) make sure that the '''Akonadi''' server is completely shut down before trying to start it again, by calling on the command line:
{{input|1=akonadictl stop}}
U kunt het afsluiten bevestigen door het uitvoeren van:
{{input|1=akonadictl status}}
Under some circumstances the Akonadi server can be stuck in a partially running state after a failure which will prevent the next attempt to start it to fail as well. Please file a bug report if you run into this problem including the self-test report of the initial problem.
Under some circumstances the '''Akonadi''' server can be stuck in a partially running state after a failure which will prevent the next attempt to start it to fail as well. Please file a bug report if you run into this problem including the self-test report of the initial problem.
=== The so-called "Gentoo-Assert" ===
=== De zogenaamde "Gentoo-Assert" ===
That's an especially nasty problem that so far only affects users of source-based distributions, most prominently Gentoo. It is named after MySQL assertions like the following example and is most likely caused by a MySQL protocol mismatch between the MySQL server and the client library or the Qt MySQL driver.
That's an especially nasty problem that so far only affects users of source-based distributions, most prominently ''Gentoo''. It is named after MySQL assertions like the following example and is most likely caused by a MySQL protocol mismatch between the MySQL server and the client library or the Qt MySQL driver.
It is extremely hard to diagnose as the assertion mentioned above are only triggered sometimes. Instead you'll get a wide range of weird symptoms:
It is extremely hard to diagnose as the assertion mentioned above is only triggered sometimes. Instead you'll get a wide range of weird symptoms:
* ASAP protocol logs show successful creation of objects which are supposedly no longer available when the next commands accesses them again.
* ASAP protocol logs show successful creation of objects which are supposedly no longer available when the next commands access them again.
* SQL protocol logs show INSERT or UPDATE commands with values that mismatch the corresponding column types and nevertheless succeed.
* SQL protocol logs show INSERT or UPDATE commands with values that mismatch the corresponding column types and nevertheless succeed.
* SQL protocol logs showing large apparently random record ids which are nevertheless considered valid.
* SQL protocol logs showing large apparently random record ids which are nevertheless considered valid.
References:
Referenties:
* http://forum.kde.org/viewtopic.php?f=20&t=61738
* http://forum.kde.org/viewtopic.php?f=20&t=61738
* http://bugs.gentoo.org/show_bug.cgi?id=267513
* http://bugs.gentoo.org/show_bug.cgi?id=267513
* https://bugs.kde.org/202623 (contains a possible solution)
* https://bugs.kde.org/202623 (bevat een mogelijke oplossing)
* http://bbs.archlinux.org/viewtopic.php?id=78358
* http://bbs.archlinux.org/viewtopic.php?id=78358
Possible solution: Rebuild the Qt MySQL driver after upgrading MySQL (which most likely caused this problem in the first place).
Mogelijke oplossing: bouw de Qt MySQL driver opnieuw na het upgraden van MySQL. MySQL is sowieso de meest waarschijnlijke oorzaak van dit probleem.
<span class="mw-translate-fuzzy">
[[Category: Systeem/nl ]]
</span>
Be warned that you should not follow this advice, without backing up your data.
After the introduction of KMail 2 in kdepim, since KDE SC 4.6.x, in order to search in emails and to get addressbooks, it is necessary to set <menuchoice>System Settings -> Desktop Search -> Enable Nepomuk Sematic Desktop </menuchoice> enabled, and check the box <menuchoice>Enable Email Indexer</menuchoice>.
If virtuoso-t occupies almost 100% of CPU cores and the system is nearly frozen, it may be a good idea to reset all.
To do the big reset you need :
{{Warning|1=This will initialize all your Kontact and KDE PIM data customization, but not remove emails data, akonadi resources (like email accounts, address books ), KMail Identities, filters and expired mail folders. However, be warned that you will lost much customization information, including ratings and other metadata. Also there is some risk here, because this reconstruction of data has bugs that may make you lose data.}}
{{Input|1=akonadictl stop
rm -rf ~/.local/share/akonadi/db_data/*
akonadictl start
# we should also clean KDE temporary folders before start KMail
You need to check <menuchoice> Settings -> Configure KMail -> Identities</menuchoice> to see whether the Sent folder is correct. Some of mine were not.
Check <menuchoice> Settings -> Configure KMail -> Accounts </menuchoice> settings and check whether the incoming folder is correct. Some of mine were not.
Check all filters, before pulling some email. I advise disabling all filters because there may be many folders incorrect or missing.
Also important is that if you have an "expired folder", check all folders to see if the receiving folder is correctly set. If you have <menuchoice>Delete permanently</menuchoice> checked you may lose important emails because expiring worked with the wrong folder.
In each <menuchoice> folder's context menu -> Folder Properties </menuchoice> check Identities, as the associated identity may also be changed or lost in any folder.
After this we are ready to [[Special:myLanguage/Akonadi_4.4/Troubleshooting#You experience long delays when sending mail|clean up Nepomuk data]] before enabling Nepomuk Semantic.
After all is cleaned , if you aren't able to read any emails, you should logout and login KDE session again to reinitialize all processes .
[[Category:System (nl)]]
[[Category:System]]
Latest revision as of 16:54, 13 February 2013
Inleiding
Deze pagina gaat voornamelijk over het oplossen van problemen met Akonadi. Storingen zijn onvermijdelijk in de vroege stadia van de migratie.
Veel mensen zijn de eerste tekenen vanAkonadi in KDE 4.4 SC en het zal velen verwarren.
Voor een korte beschrijving van het doel van Akonadi, zie de Woordenlijst.
Daar staan ook nuttige verwijzingen naar meer informatie.
Zodra de onvermijdelijke aanloopproblemen voorbij zijn, is Akonadi een power-house dat bruikbaar is voor vele toepassingen.
De structuur begrijpen
U kunt natuurlijk ook gewoonKontact gebruiken om al uw adresboeken te beheren, maar als u een bijvoorbeeld back-upsysteem hebt, wilt u weten waar uw gegevens zijn en daarmee wordt omgegaan. Dat staat beschreven op de pagina Akonadi en AddressBook
Tips voor het oplossen van problemen
Voeg bij het melden van problemen met de Akonadiserver altijd het uitgebreide zelftestrapport toe.
U kunt dit rapport aanmaken dor het dialoogvenster zelftest dat automatisch wordt weergegeven als de Akonadiserver niet kon opstarten.
De zelftest staat in de kcmmodule, die toegankelijk is via:
kcmshell4 kcm_akonadi
Het handmatig starten van de Akonadiserver vanaf de commandoregels kan ook bruikbare informatie opleveren. Start de server door in een console het volgende commando uit te voeren:
akonadictl start
Met deze opdracht kan de Akonadiserver weer gestopt worden:
akonadictl stop
Dit commando geeft meer nuttige informatie:
akonadictl status
Veelvoorkomende problemen
Kontact start niet en geeft geen informatie
Als Kontact niet start, en u ziet geen foutmeldingen, controleer dan of Akonadi draait.
Akonadi moeten starten als daarom wordt gevraagd.
Als dat op uw systeem niet werkt, start het dan voordat Kontact opstart als u gemigreerde bronnen hebt; waarschijnlijk is dat KAddressBook.
Gebruik het icoon voor Akonadi in het systeemvak, dit wordt actief na het uitvoeren van "akonadi" inKRunner, of typ de opdrachten in konsole om het te starten.
Kontact start niet, versie II
Kontact has been known to be hit after an update. If this happens, try starting KMail, KOrganizer or any of the other applications from KRunner (or Konsole). Chances are high that they will work as stand-alone apps while you find what went wrong. This mainly affects version 4.4.0.
Map niet gevonden: "/Local"
Sommige gebruikers hebben deze foutmelding gemeld als Kontact niet wilde starten.
In een aantal vroege versies van 4.4 lijkt een bug te zitten in de migratie die KMail aangeeft om te kijken ~/.local/share/Local, een map die niet was aangemaakt.
De oplossing hiervoor is om niet te proberen dit probleem te verhelpen, maar terwijl KMail en/of Kontact afgesloten zijn, de Akonadi Console te openen:
Gebruik KRunner, Alt-F2, of
"akonadiconsole" konsole
Verwijder vervolgens de bron die aangeeft voor lokale e-mail te zijn.
Nu hoort Kontact of KMail te starten, en wordt de nieuwe bron aangemaakt met een verwijzing naar ~/.local/share/local-mail.
Er staan andere nieuwe mappen in ~/.local/share/
Ja. Als uw adresboek correct is gemigreerd, wordt een nieuwe bron aangemaakt als ~/.local/share/contacts/.
Wat zijn /usr/bin/akonadi_maildir_resource en /usr/bin/akonadi_maildispatcher_agent?
The akonadi_maildir_resource is created automatically by the akonadi_maildispatcher_agent, while the latter is always started together with the Akonadi server as it provides basic functionality (e.g. sending mail) that is used by all mail applications that are (and will be) based on Akonadi. So it is ok that these two are running, as a user you can simply ignore them.
This autogenerated akonadi_maildir_resource will always point to ~/.local/share/local-mail/ which is your "Local folders" account where your local folders and emails will be stored.
E-mail wordt op dit moment in KDE SC 4.4 nog niet gemigreerd.
Nepomuk Indexing Agents zijn uitgeschakeld
Kontact werkt nu, maar u blijft de volgende melding zien:
The most common reason for this notice is that Nepomuk is simply disabled in System Settings. Please try enabling it in System Settings under Advanced -> Desktop Search -> Basic Settings by checking "Nepomuk Semantik Desktop" and clicking "Apply".
If this does not help (or if the option was already checked when you got the error) and if you have previously been using prereleases of KDE SC 4.4, you may be affected by a change to the database layout (due to an upgrade of the Virtuoso database server from version 5 to version 6; production releases of KDE SC 4.4 are expected to be shipped with Virtuoso version 6). The following commands should get it working again:
Note that the above commands will not enable Nepomuk permanently if it isn't already enabled, you have to use System Settings for that.
A running Nepomuk is necessary to have a working Akonadi, and thus a working Kontact. However, you can disable the Strigi file indexer, which is not needed for Kontact. Strigi file indexing is used for desktop searching only, which is unrelated to Kontact. Just make sure Nepomuk itself is running correctly for Kontact.
In Kontact, Nepomuk is used for many different things, ranging from displaying upcoming birthdays, over handling free/busy lists to showing a contact photo in the message viewer. If Nepomuk is not running, several different things in Kontact will cease to work. The notice is there to warn you about the reduced functionality. Enabling Nepomuk as described above fixes the problem.
U kunt controleren of Nepomuk correct draait met dit commando:
akonadictl status
Ik wil mijn huidige adresboek en agenda gebruiken. Kan dat?
Yes. When you use the Akonadi Console to add a resource it allows you to choose as Standard Addressbook - point that to your std.vcf should work fine. Migration does not destroy your old addressbook. You can continue to use it, though you will lose any benefits that Akonadi can bring. Alternatively you can have both an Akonadi addressbook and your original one, for a time, if you feel safer that way.
Ik zie geen gegevens in mijn adresboek
At the moment, the cause of this is not identified, but the cure is simple. Close Kontact, and start KAddressBook as a stand-alone application. After you close it you will be able to use it within Kontact. It seems that something is not being triggered when Kontact launches, and I expect this to be identified and fixed soon. This seems to mainly affect version 4.4.0.
Mijn contacten worden niet weergegeven als ik op Selecteren klik in KMail
Check System Settings -> Advanced tab -> KDE Resources. Make sure that your Akonadi controlled address book(s) are listed there - add them if necessary. At the same time, it's a good idea to make your main Akonadi addressbook, usually called "Personal Contacts", is set to be the default. More details of how this can be found in here.
Hoe krijg ik mijn groupwareadresboek terug?
Twee oplossingen: met het oude framework of met het nieuwe.
Old framework: In akonadiconsole, add a "KDE Address Book (traditional)". The KDE Address Book means you can set up old kresources for Akonadi. In the configuration of "KDE Address Book (traditional)", you point it to an "IMAP over KMail" KResource and in KMail, the groupware options should be enabled. This should work for Kolab, eGroupware and similar addressbooks - you will need to check the options to make sure that the correct type is selected.
New framework (only tested with Kolab): In the Akonadi configuration module add an "IMAP E-Mail Server" resource, and set up your mail server name, username and password, then click Auto-Detect. Run this command to see it:
kcmshell4 kcm_akonadi
Then add a Kolab resource. The next step is to wait for the imap resource to synchronize, which can take quite a long time. The status will appear in the Akonadi configuration module. If nothing happens, try restarting akonadiserver. After some time the Kolab addressbook(s) should appear in KAddressBook.
Er zijn lange vertragingen bij het verzenden van e-mail
Dit gaat gepaard met het bevriezen van KMail totdat de e-mail daadwerkelijk is verzonden.
A bug has been found in the way Nepomuk checks addresses, which can cause huge delays. This is fixed for SC 4.4.1. If you cannot get 4.4.1 yet, there is this work-around:
Close Kontact, or KMail and KAddressbook if you are running
stand-alone apps. Disable Strigi in SystemSettings. Stop Nepomuk, delete the database and restart nepomukserver. The actual commands you need are (as user):
This will, of course, wipe out all the database, including any tags you've
added. In theory, I understand that it's possible to do a more selective wipe
of the database. If this matters to you you can find the instructions at
this page
IMAP Resource always claims to be offline
Even though the system has an internet connection, the IMAP resource refuses
to switch to online state.
This bug is caused by a misconfigured NetworkManager installation on your system. Check the output of the following command:
20 (formerly 4), disconnected. If you have access to the internet, your NetworkManager configuration must be wrong.
70 (formerly 3), connected. The problem must be somewhere else.
It might be that one or more network interfaces are not controlled by NetworkManager. If that is your case, give the control of those interfaces to NetworkManager. It might be as simple as removing the entries for the interfaces from a text file (for example, /etc/network/interfaces). Check the help resources provided by your software distribution for more information.
Can't read any details of some messages or big delays to read it
if you aren't able to read some emails and see a message with " please wait ... ", you may logout and login KDE session to reinitialize all processes, might help.
Een aantal technische kwesties
Nepomuk
Starting with KDE 4.4, it is required that Nepomuk is running in order for Akonadi to work correctly. Akonadi will check this and display an error dialog on startup if this is not the case.
Nepomuk only works with the Virtuoso backend.
You can check whether the Nepomuk is running with the correct backend by using the Akonadi self-test dialog, as described above.
Although Nepomuk is required to be running, you can still disable Strigi file indexing, which is usually the most resource-intensive part of the Nepomuk framework.
Apparmor
Some distributions using Apparmor have it set up in a way that prevents Akonadi from running its internal database server. This can result in a variety of fuzzy error messages, including but not limited to the following:
unknown error 255 when running akonadictl
"DB error: 'Could not open required defaults file: /home/$username/.local/share/akonadi/mysql.conf"
You can solve this by running the following command with root privileges then reload apparmor:
Let op: wellicht gebruikt u Apparmor zonder dat dit zichtbaar is in de proceslijst.
Also note that some distributions ship an additional mysqld binary called mysqld-akonadi which has AppArmor set up correctly. If that's the case on your system and you see this problem nevertheless, there are two possible reasons:
Akonadi still uses mysqld instead of mysqld-akonadi. You can change that in Systemsettings -> Advanced -> Akonadi -> Server configuration.
AppArmor is not setup correctly for mysqld-akonadi either. Try running the "aa-complain" command noted above with mysqld-akonadi instead of mysqld.
---
You will also experience this problem if you are running an encrypted home directory using encryptfs combined with AppArmor as the Akonadi apparmor profile currently does not account for an ecrypted home (common with Ubuntu Jaunty users). Error messages with include:
dmesg produces:
ecryptfs_do_create: Failure to create dentry in lower fs; rc = [-13]
ecryptfs_create: Failed to create file inlower filesystem
Akonadi geeft de volgende foutmeldingen:
Akonadi server process not registered at D-Bus
Dit is op te lossen door het bestand "/etc/apparmor.d/usr.sbin.mysqld-akonadi" aan te passen.
Voeg onder de regel:
@{HOME}/.local/share/akonadi/** rwk,
Voeg een nieuwe regel toe:
@{HOME}/.Private/** rwk,
Herstart apparmor en herstart akonadi.
Ontbrekende voorwaarde
Om Akonadi te kunnen gebruiken, moeten de volgende packages geïnstalleerd zijn. Afhankelijk van uw distributie kunnen de namen anders zijn:
De MySQL server (die heet mysql in openSUSE)
Dee Qt4 MySQL plugin (die heet libqt4-sql-mysql in openSUSE)
If you compile Qt4 yourself, make sure to tell the configure script to build in MySQL support by passing it the following option:
-plugin-sql-mysql
If "configure" cannot locate the necessary MySQL client code (i.e, says "MySQL support cannot be enabled due to functionality tests") then ensure that the corresponding package is installed (typically called [lib]mysql[client]-dev[el]). Also, depending on the install location of the MySQL headers, additional parameters to "configure" might be needed (eg. "-I /usr/include/mysql" on OpenSuse).
Als u de Qt4 rechtstreeks van Nokia krijgt, zoals een download van qt-sdk-linux-x86_64-opensource-2009.05.bin</code, dan krijgt u een foutmelding bij Test 1 tijdens het uitvoeren van het commando "akonadictl start":
Database driver not found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration.
The following drivers are installed: QSQLITE.
Make sure the required driver is installed.
U hebt de driver libqsqlmysql.so nodig.
Helaas is deze driver is geen onderdeel van de distributie (tot januari 2010).
U moet de broncode compileren. Download dit bestand:
qt-everywhere-opensource-src-4.6.0.tar.bz
Then configure and make as above. But the make install doesn't copy the driver. So you have to copy it by yourself:
But the Revision 4.6.1, such as qt-sdk-linux-x86_64-opensource-2010.xx.bin has the driver you needed.
But it might be necessary to bind again the libqsqlmysql.so if the libmysqlclient.so has changed to a newer version.
Omgeving instellen
The Akonadi server searches for Akonadi agents and resources in the paths defined in the XDG_DATA_DIRS environment variable. If Akonadi complains about not finding agents or resources, check if this variable is set correctly. Also keep in mind that even if set in a current console session, it might not have been set when starting the server. Starting the server manually in the current console session excludes this cause.
Als het logboek van de MySQL server de volgende foutmelding bevat, dan is uw MySQL server gebouwd zonder ondersteuning voor InnoDB, wat nodig is om gebruik te maken van Akonadi, of InnoDB moet geladen worden in uw instellingenbestand mysql.conf:
#sql_mode=strict_trans_tables <- Add underneath this line
#plugins
plugin_dir=usr/lib/mysql/plugin < - This may be a different path
plugin-load=ha_innodb.so
Table 'mysql. servers' doesn't exist
Als het logboek van MySQL server de volgende foutmelding bevat, dan hebt u waarschijnlijk nog instellingenbestand voor MySQL:
[ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
[ERROR] Cannot open mysql.db
[ERROR] Cannot open mysql.user
[ERROR] Cannot open mysql.event
Copy it from /usr/share/config/akonadi/mysql-global.conf into ~/.config/akonadi/mysql-local.conf. (For debian and openSuSE users the file is located in /etc/akonadi/mysql-global.conf). Then open it and uncomment the line sql_mode=strict_trans_tables. After that, you may get the following errors:
[ERROR] Plugin 'InnoDB' init function returned error.
[ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
[ERROR] Unknown/unsupported table type: innodb
[ERROR] Aborting
If so, then in the same file find the line that starts just like the one above (which you have uncommented), but has additional parameters, separated by commas (something like sql_mode=strict_trans_tables,strict_all_tables, ...etc). Comment the shorter sql_mode=... line and uncomment the longer one.
In openSUSE 11.2 lost de volgende opdracht het probleem op:
This is a summary of other entries here for those upgrading from Kubuntu 9.10 to 10.04 who may have been using a personal package archive (PPA) for KDE 4.3 for bug fixes.
Install missing prerequisites. Remove previous akonadi cache. Start the akonadi service. Install the database. Upgrade the database. Stop and restart the akonadi service.
In addition to the Kubuntu 10.04 remedy above, problems trying to add a Vcard directory may require the following command while Akonadi is not running:
rm -rf $HOME/.config/akonadi
Can't initialize character set latin1
Als u de volgende foutmelding krijgt bij het starten van Akonadi, dan gebruikt u waarschijnlijk een versie van MySQL server met een versie hoger dan 5.1.42:
Character set 'latin1' is not a compiled character set and is not specified in the '/usr/share/mysql/charsets/Index.xml' file
Nepomuk QueryServer interface not available!
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
DataStore::unhideAllPimItems()
Character set 'latin1' is not a compiled character set and is not specified in
the '/usr/share/mysql/charsets/Index.xml' file
Database error: Cannot open database.
Last driver error: "QMYSQL: Unable to connect"
Last database error: "Can't initialize character set latin1 (path:
/usr/share/mysql/charsets/)"
Database error: Cannot open database.
Last driver error: "QMYSQL: Unable to connect"
Last database error: "Can't initialize character set latin1 (path:
/usr/share/mysql/charsets/)"
Er is een bekende regressie in MySQL 5.1.43 en 5.1.44 waardoor MySQL niet kan worden gestart.
If you had problems starting Akonadi and fixed those (such as a missing package or the Apparmor problem) make sure that the Akonadi server is completely shut down before trying to start it again, by calling on the command line:
akonadictl stop
U kunt het afsluiten bevestigen door het uitvoeren van:
akonadictl status
Under some circumstances the Akonadi server can be stuck in a partially running state after a failure which will prevent the next attempt to start it to fail as well. Please file a bug report if you run into this problem including the self-test report of the initial problem.
De zogenaamde "Gentoo-Assert"
That's an especially nasty problem that so far only affects users of source-based distributions, most prominently Gentoo. It is named after MySQL assertions like the following example and is most likely caused by a MySQL protocol mismatch between the MySQL server and the client library or the Qt MySQL driver.
Mogelijke oplossing: bouw de Qt MySQL driver opnieuw na het upgraden van MySQL. MySQL is sowieso de meest waarschijnlijke oorzaak van dit probleem.
Be warned that you should not follow this advice, without backing up your data.
After the introduction of KMail 2 in kdepim, since KDE SC 4.6.x, in order to search in emails and to get addressbooks, it is necessary to set System Settings -> Desktop Search -> Enable Nepomuk Sematic Desktop enabled, and check the box Enable Email Indexer.
If virtuoso-t occupies almost 100% of CPU cores and the system is nearly frozen, it may be a good idea to reset all.
To do the big reset you need :
Warning
This will initialize all your Kontact and KDE PIM data customization, but not remove emails data, akonadi resources (like email accounts, address books ), KMail Identities, filters and expired mail folders. However, be warned that you will lost much customization information, including ratings and other metadata. Also there is some risk here, because this reconstruction of data has bugs that may make you lose data.
akonadictl stop
rm -rf ~/.local/share/akonadi/db_data/*
akonadictl start
# we should also clean KDE temporary folders before start KMail
rm -rf /var/tmp/kdecache-$USER /tmp/ksocket-$USER /tmp/kde-$USER
You need to check Settings -> Configure KMail -> Identities to see whether the Sent folder is correct. Some of mine were not.
Check Settings -> Configure KMail -> Accounts settings and check whether the incoming folder is correct. Some of mine were not.
Check all filters, before pulling some email. I advise disabling all filters because there may be many folders incorrect or missing.
Also important is that if you have an "expired folder", check all folders to see if the receiving folder is correctly set. If you have Delete permanently checked you may lose important emails because expiring worked with the wrong folder.
In each folder's context menu -> Folder Properties check Identities, as the associated identity may also be changed or lost in any folder.
