I don't know what fixed it, but it works for me again:
akonadi-backend-mysql 4:22.04.3-1
akonadi-server4:22.04.3-1
kontact 4:22.04.3-1
libkf5libkdepim5:amd644:22.04.3-1
libqt5sql5-
It seems to me that indeed akonadiserver is the culprit. I kept kontact
running and only stopped akonadiserver, killed mariadb and resarted
akonadiserver. Then kontact started to work again.
More info: I suspect that this is due to a deadlock in the db updates,
akonadiserver even logs this:
org
Note that my previous message on https://bugs.debian.org/cgi-bin/
bugreport.cgi?bug=1010576 is incomplete, please see the referenced Message
Part 2 (https://bugs.debian.org/cgi-bin/bugreport.cgi?
att=1;bug=1010576;msg=25) for the full contents.
I collected some information that might help with debugging, unfortunately some
output uses
German localization, I can translate these if needed:
In the shell where I started akonadi with akonadictl start, I got this output
(many
lines duplicated and removed for brevity):
"Das Objekt existiert
Exactly, but be careful with kill -9. I once broke my database with it such
that mariadb would not even start anymore. I had to delete the entire directory
and let akonadi recreate it from scratch.
I got the same thing today on a vmware virtual machine running Debian stable
2.6.32-5-amd64 #1 SMP.
ping still worked, but nothing else. The vmware console showed the same
message about task bdi-default being blocked.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
6 matches
Mail list logo
