https://bugs.kde.org/show_bug.cgi?id=361485
Daniel Vrátil changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=361485
--- Comment #7 from priv...@bernhard-lindner.de ---
Seems I am experiencing this an my new Kubuntu 16.04 system too. Is there a
workaround that allow my to set up the system correctly soon?
--
You are receiving this mail because:
You are the assignee f
https://bugs.kde.org/show_bug.cgi?id=361485
priv...@bernhard-lindner.de changed:
What|Removed |Added
CC||priv...@bernhard-lindner.de
--
Yo
https://bugs.kde.org/show_bug.cgi?id=361485
--- Comment #6 from Lars Tangvald ---
Launchpad bug report:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1572100
--
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim
https://bugs.kde.org/show_bug.cgi?id=361485
--- Comment #5 from Lars Tangvald ---
The other issue is that since MySQL 5.7 is significantly more strict by default
than 5.6, the sql scripts used for database init will fail.
Ideally these would be gone through and updated, but a possible workaround
https://bugs.kde.org/show_bug.cgi?id=361485
--- Comment #4 from Lars Tangvald ---
Created attachment 98462
--> https://bugs.kde.org/attachment.cgi?id=98462&action=edit
Updated mysql_install_db options for MySQL 5.7
This patch will update mysql_install_db usage in akonadi to work with MySQL
5.7
https://bugs.kde.org/show_bug.cgi?id=361485
Lars Tangvald changed:
What|Removed |Added
CC||lars.tangv...@oracle.com
--- Comment #3 from La
https://bugs.kde.org/show_bug.cgi?id=361485
--- Comment #2 from Luis Silva ---
The --verbose flag was not the appropriate one. Here is the true result of
trying to start the mysqld instance by hand. The problem is clear, akonadi is
not handling the update correctly and mysql.plugin is not either
https://bugs.kde.org/show_bug.cgi?id=361485
Luis Silva changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
CC|