http://bugzilla.opensuse.org/show_bug.cgi?id=1142680 Bug ID: 1142680 Summary: Akonadi server fails to start after upgrade to Tumbleweed 20190721 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: rodney.baker@iinet.net.au QA Contact: qa-bugs@suse.de Found By: Community User Blocker: --- Akonadi server fails to start after I upgraded to 20190721 snapshot. Running "akonadictl start --verbose" produces this output: org.kde.pim.akonadiserver: Found mysql_install_db: "/usr/bin/mysql_install_db" org.kde.pim.akonadiserver: Found mysqlcheck: "/usr/bin/mysqlcheck" org.kde.pim.akonadiserver: Using mysqld: "/usr/sbin/mysqld" org.kde.pim.akonadiserver: Database "akonadidb" opened using driver "QMYSQL" org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: checking table "SchemaVersionTable" org.kde.pim.akonadiserver: "ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0" 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: terminating connection threads org.kde.pim.akonadiserver: terminating service threads org.kde.pim.akonadiserver: Shutting down "NotificationManager" ... org.kde.pim.akonadiserver: stopping db process org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally... Akonadi server appears to be trying to initialise the db from scratch, when the db already exists and was working before the upgrade. I've confirmed that the database server (mysqld/MariaDB) is running and accessible to the akonadi user, the tables exist and contain data, and the columns akonadi is trying to create are already present with the correct data type. Dropping the column results in an error on the next column; dropping the SchemaVersionTable results in the table being successfully created but the error then repeats on the next table (ResourceTable) that akonadi is attempting to modify. Again, this has only occurred after the upgrade to snapshot 20190721 - it was working fine prior to the upgrade. -- You are receiving this mail because: You are on the CC list for the bug.