severity 969171 normal thanks Dear Eric.
Akonadi will use whatever database is set in the configuration file, by default on first startup MySQL if the MySQL backend has been installed at first startup. So if you use it with an existing home directory that has MySQL specified as database backend it needs the MySQL database backend of Akonadi to operate with the existing configuration. See the file: '~/.config/akonadi/akonadiserverrc'. This can happen as easily as starting once with the MySQL backend installed, as Plasma starts Akonadi automatically in its default configuration. Then you have an empty MariaDB based Akonadi. If you then switch to PostgreSQL this error occurs. Please ask on debian-kde and/or upstream kdepim-users mailing list for support. The Debian bug tracker is not for user support questions. Also review previous threads on this topic there. Note that on switching the database Akonadi will start anew and some information only stored in the database will be lost. I think it is not a bug of the package. But it is definitely not severity grave as Akonadi is perfectly usable here in exact the same version (usable to the extent Akonadi works reliable, but that is an upstream issue). So downgrading severity to normal. I have seen repeatedly seen that you set too high bug severity. If the package does not work for me does not mean that its automatically grave severity. Especially when it is, as I assume, a configuration error. So please refrain from setting grave when it isn't. It just causes additional work for the already overloaded Debian Qt/KDE team. If you are unsure please ask first in debian-kde mailing list. That is part of what it is there for. Best, -- Martin
