Kalendar stopped working

General system Applications
1

I am not sure if this is the right category, but anyway, hoping there is someone here that has an idea how to tackle this issue.

One of my favorite program, Kalendar (for KDE) has stopped working. I am sure this happended because I was managed to unplug my laptop while it was updating, which was instant shut off (my battery doesn’t hold a charge). Miraculously only this program stopped working, which is bit annoying, cause it actually helps me stay a bit organized.

Now, when trying to start Kalendar through terminal, I get this

QML debugging is enabled. Only use this in a safe environment.
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/olividir/.local/share/akonadi/mysql.conf", "--datadir=/home/olividir/.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-06 21:18:36 0 [Note] /usr/bin/mysqld (server 10.8.3-MariaDB) starting as process 11857 ...\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.akonadicore: Could not start/stop Akonadi!
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
[1]    11845 segmentation fault (core dumped)  kalendar
~ ❯ org.kde.pim.akonadiserver: database server stopped unexpectedly                        ✘ SEGV 6s 21:18:42
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/olividir/.local/share/akonadi/mysql.conf", "--datadir=/home/olividir/.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-06 21:18:41 0 [Note] /usr/bin/mysqld (server 10.8.3-MariaDB) starting as process 11876 ...\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...

I am definiatly not comfortable messing with these files in this log.

My inxi can be found here https://clbin.com/mNRnd

If anyone has an idea how to fix this, please let me know.

2

It is possible that the marisdb/mysql version changed and the database needs to be updated. It happens every few years.

I don’t use akonadi to be able to test it out but you might consider trying the steps here:

1 Like
3

Downgrading mariadb mariadb-client and mariadb-libs seems to have worked for me, thank you for that.
However I am not able to update with
mariadb-upgrade -S /run/user/1000/akonadi/mysql.socket
because there is no file in this location.

Thank you for pointing me in the correct direction, but I guess it is a work-around :slight_smile:

Spoke too soon, but for some reason
mariadb-upgrade -S /run/user/1000/akonadi/mysql.socket
won’t allow me to upgrade, and using --force does not work for me. Anyway, I’ll figure it out.

Edit 07.June 2022
Kalendar starts even if mariadb is not updated, so this is solved.

4

All the more reason for isolated apps?

@olividir I know this is not what you asked but maybe you wanna try the flatpak.

5

I am aware of Flatpak, but I am not there to run only flatpaks. It is however something that might be future solution.

6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.