After upgrading the PIM Applications from the ubuntu packages to the kde neon user packages the akonadiserver fails to start See the attached upgrade and start log. Reproducible: Always Steps to Reproduce: 1. Upgrade Packages 2. start akonadi: `akonadictl start` Actual Results: Akonadi does not start Expected Results: Akonadi starts
Created attachment 100445 [details] Upgrade log
Created attachment 100446 [details] Start log
To exclude errors from my old configuration I also tried `akonadictl --instance mynewcustominstance332 start`. But I get the same result. The start log is nearly the same (different database/config paths) and akonadi tries to initialize the database which also fails: mysqld: [ERROR] Could not open required defaults file: /etc/xdg/akonadi/mysql-global.conf mysqld: [ERROR] Fatal error in defaults handling. Program aborted!
This problem has been confirmed by several people on the Neon Telegram group including me. Here is my start log: https://paste.kde.org/pidq3mblw
which flavour of neon?
User edition
Can you open /etc/xdg/akonadi/mysql-global.conf ? Do you have /var/lib/mysql-files ?
Please post output of dpkg --get-selections | grep mysql I'm curious to see if you have the full mysql-server installed Do you know if you intend to have the full server installed?
/etc/xdg/akonadi/mysql-global.conf: https://paste.kde.org/pqluaqtke Creating directory /var/lib/mysql-files with 755 rights solves the problem. Full mysql-server installed, not intended.
> Can you open /etc/xdg/akonadi/mysql-global.conf ? Yes https://paste.kde.org/pbshldhur/j4tbuh > Do you have /var/lib/mysql-files ? No > Please post output of : dpkg --get-selections | grep mysql akonadi-backend-mysql install libmysqlclient-dev install libmysqlclient20:amd64 install libmysqld-dev install libqt4-sql-mysql:amd64 install libqt5sql5-mysql:amd64 install mysql-client-core-5.7 install mysql-common install mysql-server-core-5.7 install > Creating directory /var/lib/mysql-files solves the problem. I can confirm this
*** Bug 366512 has been marked as a duplicate of this bug. ***
added /var/lib/mysql-files to neon-settings
Creating directory /var/lib/mysql-files solves this problem for me as well. This is on a fresh install of 16.10.
fixed in neon-settings