Arch Linux

msl09

Member

Registered: 2022-10-01

Posts: 17

Possible issue with akonadi

When logging in with a new user in kde, if mariadb is installed, akonadi creates a user database with mariadb. If mariadb is later removed the kde panels hang on login for a minute or so as akonadi tries and fails to open the user database. The workaround I've come up with was to remove the database files.

According to a KDE developer akonadi should depend on mariadb (it's currently an optional dependency in arch).

Link to the discussion: https://discuss.kde.org/t/when-replacin … -bug/50325

ilsensine

Member

Registered: 2013-03-26

Posts: 34

Re: Possible issue with akonadi

Can you try to migrate akonadi to sqlite before removing mariadb?
akonadi-db-migrator --newengine sqlite

arojas

Developer

From: Spain

Registered: 2011-10-09

Posts: 2,306

Re: Possible issue with akonadi

When you removed mariadb, pacman warned you about it:

checking dependencies...
:: akonadi optionally requires mariadb: MariaDB backend

If you still went ahead with it, it's not Arch's fault.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,890

Re: Possible issue with akonadi

https://wiki.archlinux.org/title/KDE#Akonadi supports an array of mutually exclusive backends that you can select.
There're not "backend" packages, the debian stuff is just global pre-configurations: https://packages.debian.org/trixie/all/ … l/filelist

=> If you want to replace the backend, you'll have to edit your users akonadi config.
Afaiu on debian you're forced to globally select a backend fro all users because of the mutually exclusive dependencies on specific configurations.

Akonadi (clients) synchronously accessing its backend in the GUI thread is questionable code/API design.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc