I'm using Manjaro, and last night updated my Kontact (through Pamac) to the version 5.20.2 (22.04.2).
After reboot, the app failed to work:
in Mail, Calendar, Contact, To Do list, the same error shows: The Akonadi personal information management service is not operational.

I tried the method on Manjaro forum (https://forum.manjaro.org/t/the-akonadi ... onal/53082), rebooted, and still the same.
I tried reinstalling the Akonadi and Kontact, rebooted, and still failed to get it work.

Any help?
Thanks.

Same Problem for me on EndeavourOS (Kmail and Kalendar).

This is what it shows in the Terminal when starting KMail:
org.kde.pim.akonadicontrol: Service org.freedesktop.Akonadi.Control.lock already registered, terminating now.
Error loading text-to-speech plug-in "speechd"
Cannot initialize model with data QJsonObject(). missing: QJsonValue(string, "urls")
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
org.kde.pim.akonadicore: Job error: "" for collection: QVector()
org.kde.pim.akonadicore: Job error: "" for collection: QVector()
org.kde.pim.messagelist: Failed to load tags ""
org.kde.pim.mailcommon: failed to retrieve tags ""
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial connection!
org.kde.pim.akonadiserver: executable: "/usr/bin/mysqld"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/johannes-eos/.local/share/akonadi/mysql.conf", "--datadir=/home/johannes-eos/.local/share/akonadi/db_data/", "--socket=/run/user/1000/akonadi/mysql.socket", "--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2022-06-13 19:40:05 0 [Note] /usr/bin/mysqld (server 10.8.3-MariaDB) starting as process 8796 ...\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
org.kde.pim.kmail: ""

Hello,

I seem to have the same problem (on Artix):

Code: Select all

~> akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl:    done.
~> Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial connection!
org.kde.pim.akonadiserver: executable: "/usr/bin/mysqld"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/micha/.local/share/akonadi/mysql.conf", "--datadir=/home/micha/.local/share/akonadi/db_data/", "--socket=/run/user/1000/akonadi/mysql.socket", "--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2022-06-14 12:36:40 0 [Note] /usr/bin/mysqld (server 10.8.3-MariaDB) starting as process 7778 ...\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...

Here (https://bbs.archlinux.org/viewtopic.php?pid=2040086) post-factum suggested to look at

Code: Select all

cat ~/.local/share/akonadi/db_data/mysql.err
2022-06-14 12:36:40 0 [Warning] option 'innodb-log-buffer-size': unsigned value 1048576 adjusted to 2097152
2022-06-14 12:36:40 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2022-06-14 12:36:40 0 [Note] InnoDB: Number of transaction pools: 1
2022-06-14 12:36:40 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-06-14 12:36:40 0 [Note] InnoDB: Using Linux native AIO
2022-06-14 12:36:40 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-06-14 12:36:40 0 [Note] InnoDB: Completed initialization of buffer pool
2022-06-14 12:36:40 0 [ERROR] InnoDB: File ./ib_logfile0 was not found
2022-06-14 12:36:40 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2022-06-14 12:36:40 0 [Note] InnoDB: Starting shutdown...
2022-06-14 12:36:41 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-06-14 12:36:41 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-06-14 12:36:41 0 [ERROR] Unknown/unsupported storage engine: innodb
2022-06-14 12:36:41 0 [ERROR] Aborting

And sure enough - as suggested here (https://www.mail-archive.com/kdepim-bugs@kde.org/msg134634.html) -

Code: Select all

touch ~/.local/share/akonadi/db_data/ib_logfile0

did it for me.
Akonadi and thus Kontact work again, in my instance that is.

Since this bug seems to stem from akonadi's issue, can we expect KDE to come out with a solution update soon?
it has been 4 days, and it affects the major product bundle - Kontact from KDE.
If KDE is giving no priority to such bug, I am more inclined to switch to other less problematic app.

shurato wrote:Since this bug seems to stem from akonadi's issue, can we expect KDE to come out with a solution update soon?
it has been 4 days, and it affects the major product bundle - Kontact from KDE.
If KDE is giving no priority to such bug, I am more inclined to switch to other less problematic app.

Well, ~/.local/share/akonadi/db_data/ib_logfile0 is mysql's bussines, not akonadi's so I guess blaming the KDE developers wouldn't be correct.

FWIW no such issue here (Slackware64 -current fully uptodate).

richarson wrote:Well, ~/.local/share/akonadi/db_data/ib_logfile0 is mysql's bussines, not akonadi's so I guess blaming the KDE developers wouldn't be correct.

FWIW no such issue here (Slackware64 -current fully uptodate).

I dun blame KDE.
But I wonder if mysql gonna know what happened to Kontact, and if they see any benefits to resolve KDE issues, since there is no problem with Slackware's Kontact?
And if mysql is not gonna actively resolve this Kontact issue, who will?

Manjaro just bumped the version of Kontact to 22.04.2-1.
And there is absolutely no love from anyone to resolve this KDE issue - same error.

This looks like bug 454948.