Akonadi fresh install fails to start with MySQL 5.7

Bug #1572100 reported by Lars Tangvald
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
akonadi (Ubuntu)
Fix Released
High
Philip Muškovac

Bug Description

On a fresh install with MySQL 5.7, akonadi will fail to start up because
a) mysql_install_db is run with options that are removed in 5.7
--force has been removed, and to keep the old behavior we need to add --insecure and --basedir=/usr

b) Database init sql scripts are rejected by 5.7's stricter default mode: http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html
5.7 is more restrictive of allowed values for different column types (no data truncation, no 0-dates, etc.)
A workaround is to add sql_mode=NO_ENGINE_SUBSTITUTION, which was the default value in 5.6

Bug is also reported, with suggested fixes, in the kde tracker: https://bugs.kde.org/show_bug.cgi?id=361485

Tags: kubuntu xenial
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in akonadi (Ubuntu):
status: New → Confirmed
Revision history for this message
Silicomancer (private-g) wrote :

Is there a workaround that I can use to make my new Kubuntu 16.04 system work soon?

Philip Muškovac (yofel)
Changed in akonadi (Ubuntu):
assignee: nobody → Philip Muškovac (yofel)
importance: Undecided → High
milestone: none → ubuntu-16.04
status: Confirmed → In Progress
tags: added: kubuntu xenial
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package akonadi - 4:15.12.3-0ubuntu6

---------------
akonadi (4:15.12.3-0ubuntu6) xenial; urgency=medium

  * kubuntu_fix_mysql_db_creation_57.diff:
    Fix MySQL DB first run setup (LP: #1572100)
    (Thanks to Lars Tangvald for the patches)
  * Add DEP3 headers for kubuntu_disable_secure_file_priv_check.diff

 -- Philip Muškovac <email address hidden> Wed, 20 Apr 2016 10:25:18 +0200

Changed in akonadi (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.