I don't know what the consequences of this are. But when I open the "AkonadiTray" configuration of Akonadi dialog and there go to "Test...", I see a red X on "MySQL service log contains errors." The only error in this file (the others look like Info or Warning) is this: [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist On the FAQ page of Akonadi http://userbase.kde.org/Akonadi_4.4/Troubleshooting I am told that this error means I should place some config file into ~/.config/akonadi/mysql-local.conf . In my view, this is a bug. If akonadi wants that config file there, it should create it there when akonadi starts for the first time. By default the user should not be expected to edit any akonadi-specific config files just to make akonadi work. (Also, I'm not sure if this is actually a "problem", but I have a feeling that my akonadi is not working properly, so I'm trying to find out anything that could be wrong with it. Of course, ideally, a fresh akonadi installation should work without any error messages in any logs...) Reproducible: Always Steps to Reproduce: 1. Install akonadi and set it to use an internal MySQL. 2. Open the AkonadiTray > Settings and check the "Test..." button from the second tab. Actual Results: This error message is shown in a red question mark and there is a FAQ on the web that tells me how to edit or modify an Akonadi config file manually. Expected Results: The Akonadi should set up its own config files in such a way that it works. If this is something that the user can choose one way or another, it should be configurable in a user interface. If this is something that can be "fixed" with no choices to be made, akonadi should fix itself.
Created attachment 75106 [details] Details of akonadi selftest
Created attachment 75107 [details] Screenshot of Akonadi Selt-Test Hi, I have the same problem. I have uploaded the error log and a screenshot of the self-test window. My installed versions: christian@christian:~$ dpkg -l|grep akonadi ii akonadi-backend-sqlite 1.7.2-1 ii akonadi-server 1.7.2-1 ii libakonadi-contact4 4:4.8.4-1 ii libakonadi-kabc4 4:4.8.4-1 ii libakonadi-kcal4 4:4.8.4-1 ii libakonadi-kde4 4:4.8.4-1 ii libakonadi-kmime4 4:4.8.4-1 rc libakonadiprivate1 1.3.1-3+squeeze1 ii libakonadiprotocolinternals1 1.7.2-1 My system: Linux version 3.2.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-12) ) #1 SMP Debian 3.2.32-1 I have not installed Akonadi by myself. It has been installed automatically with kde / kmail.
I have deleted my whole .kde directory and now everything works again. So this bug can be closed, I think.
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.