Source: akonadi Version: 4:18.08.3-5 Severity: important Forwarded: https://bugs.kde.org/show_bug.cgi?id=399167
Symptoms: After a while Akonadi stops responing any request and you can not interact with Akonadi anymore. It seems to hit many people rather badly -- akonadi won't answer to any requests once hitting that bug, and even a reboot only help very temporarily (until the faulty folder gets synced again). Upstream has already proposed patches for this bug see either https://bugs.kde.org/show_bug.cgi?id=399167 these to patches should fix this bug: https://commits.kde.org/akonadi/15c91a0ac93051465b37807efceb6e9fd36cb73b https://commits.kde.org/akonadi/4fb179ce46ad3e7da8b25c921b0c8a68f9dfb4ee -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
