Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#63209 - [akonadi] akonadi 19.04.2-4 doesn't start when using MariaDB backend

Attached to Project: Arch Linux
Opened by mr stone (xtroce) - Tuesday, 16 July 2019, 12:22 GMT
Last edited by Antonio Rojas (arojas) - Friday, 26 July 2019, 11:49 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Antonio Rojas (arojas)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


It is a similar problem as the bug:

after updating akonadi does not start with following error:

org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: Running DB initializer
org.kde.pim.akonadiserver: "\nSql error: Duplicate column name 'version' QMYSQL: Unable to execute query\nQuery: ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0"
org.kde.pim.akonadiserver: Unable to initialize database.
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...

steps to reproduce:

install akonadi with a previous version and external Mariadb
then update akonadi and do

akonadictl start
This task depends upon

Closed by  Antonio Rojas (arojas)
Friday, 26 July 2019, 11:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  akonadi 19.04.3-2
Comment by Antonio Rojas (arojas) - Tuesday, 16 July 2019, 12:39 GMT
Please test downgradind akonadi to 19.04.2-3 (it has to be this exact version)
Comment by mr stone (xtroce) - Tuesday, 16 July 2019, 13:09 GMT
akonadi-19.04.2-3 works
Comment by Antonio Rojas (arojas) - Sunday, 21 July 2019, 17:43 GMT

If you use an external db you're expected to use akonadi's settings from /etc/xdg/akonadi/mysql-global.conf, especially lower_case_table_names=1