Package: akonadi-backend-mysql Version: 4:18.08.1-1 Followup-For: Bug #910902
I was able to reproduce the issue as Ian described, exactly as he described it. I had just reinstalled Debian and switched to KDE as my new desktop environment. I tried opening KMail bu tthe Akonadi service wasn't able to run. Looking in journalctl, I saw the same errors that Ian had described. Running `akonadictl start` from the terminal verified this, and gave me the same errors. I then followed Ian's workaround and created the db_data directory myself using the command `mkdir ~/.local/share/akonadi/db_data` and tried running Akonadi again from the command line, which worked without error. I rebooted to make sure Akonadi was completely offline, then ran KMail again, which worked fine. After quitting KMail and shutting down Akonadi with `akonadictl stop`, I renamed the db_data directory to 'db_data.test', and ran `akonadictl start` again, which gave me the same errors as before. Restoring the name from 'db_data.test' back to 'db_data' again fixed the issue. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages akonadi-backend-mysql depends on: ii default-mysql-client-core 1.0.4 ii default-mysql-server-core 1.0.4 ii libqt5sql5-mysql 5.11.3+dfsg-2 ii mariadb-client-core-10.1 [virtual-mysql-client-core] 1:10.1.37-3 ii mariadb-server-core-10.1 [virtual-mysql-server-core] 1:10.1.37-3 Versions of packages akonadi-backend-mysql recommends: ii akonadi-server 4:18.08.1-1+b2 akonadi-backend-mysql suggests no packages. -- no debconf information
