After upgrading to kde-apps to 18.12.3, korganizer does not start because akonadi could not be started. This again fails as follows:
$ akonadictl start
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: Running DB initializer
org.kde.pim.akonadiserver: DB initializer done
org.kde.pim.akonadiserver: SQL error when updating table PartTable
org.kde.pim.akonadiserver: Query: DROP TABLE PartTable_new
org.kde.pim.akonadiserver: Error: table PartTable_new has 7 columns but 8 values were supplied Unable to execute statement
org.kde.pim.akonadiserver: Update failed
org.kde.pim.akonadiserver: Failed to commit transaction for database update
org.kde.pim.akonadiserver: Unable to initialize database.
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
The partial fix from linked bug is already in 18.12.3, so I'm not sure what issue they really fixed.
Please note that using sqlite backend is strongly discouraged.
I changed the mysql by setting
in the ~.config/akonadi/akonadiserverrc configuration file. Restarting akonadiserver works again. (Of course, calendar entries have been fetched from the davcal server again...)
(In reply to Andreas Sturmlechner from comment #1)
> Please note that using sqlite backend is strongly discouraged.
Hence, the sqlite use-flag should be masked?
(In reply to Stefan Huber from comment #2)
> Hence, the sqlite use-flag should be masked?
I would do that in a heartbeat, but it is unpopular.
Instead, each akonadi[sqlite] pkg_setup warns:
* We strongly recommend you change your Akonadi database backend to either MySQL
* or PostgreSQL in your user configuration.
* In particular, kde-apps/kmail does not work properly with the sqlite backend.