https://bugs.kde.org/show_bug.cgi?id=386716
--- Comment #3 from Michal Kec (MiK) <k...@kecnet.cz> ---
There are two issues simultaneously.
1. Apparmor profile doesn't know MariaDB config files
Workaround: Open the file /etc/apparmor.d/usr.sbin.mysqld-akonadi and add
following lines "somewhere in the middle":
/etc/mysql/mariadb.conf.d/ r,
/etc/mysql/mariadb.conf.d/* r,
/etc/mysql/mariadb.cnf r,
2. MariaDB vs. MySQL binary files incompatibility. Since you already can have
database files generated by MySQL, MariaDB can't deal with them and dies.
Workaround: Delete everything in ~/.local/share/akonadi/db_data and restart
akonadi to let it create brand new database. It's just a metadata cache after
all.
Akonadi maintainers should definitely take care of the first issue. I'm not
sure how to fix the second one. The DB engine should detect the incompatibility
and either delete broken database, or try to migrate. Further reading:
https://mariadb.com/kb/en/library/mariadb-vs-mysql-compatibility/
--
You are receiving this mail because:
You are watching all bug changes.
