Hello I’ve a problem whit mail list. So when I want delete a single mail by canc key all mail list disappear. So I must to change folder and return to previous folder to show the rest. I use kmail 5 under Slackware 15.0 s stable.
that list blanking after delete is an akonadi refresh hang for me too.
quit kmail, run:
akonadictl restart
then open kmail again.
if it keeps doing it, say which kmail / akonadi versions you are on. akonadictl vacuum after a restart sometimes clears the stuck collection view.
Thanks! I restart akonadi on mail accout than it works. So I test in this next days!
If you have a recent KMail version, the “vacuum” is not supported by the current default Akonadi database backend –
> akonadictl vacuum
Vacuum not supported for this database backend. (Sqlite backend)
>
You have to use “akonadictl fsck” …
> kmail --version
kmail2 6.8.1 (26.08.1)
>
> kinfo
Operating System: openSUSE Tumbleweed 20260921
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Kernel Version: 7.2.6-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 8600G w/ Radeon 760M Graphics
Memory: 34 GB of RAM (32.8 GB usable)
Graphics Processor: AMD Radeon 760M Graphics
>
kmail2 5.19.1 (21.12.1)
Operating System: Slackware 15.0
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.3
Kernel Version: 5.15.209 (64-bit)
Graphics Platform: X11
Processors: 12 × 12th Gen Intel® Core™ i5-12600
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA RTX 2000 Ada Generation/PCIe/SSE2
vacuum and fsck do different things.
The latter is essentially checking (and if possible fixing) internal inconsistencies, e.g. finding cache file no longer referenced by any item (email, calendar or addressbook entry).
This works regardless of database backend because it works on a layer above.
The former is a database specific method of optimizing the database, e.g. “compacting” the database files.
Not all DB engines support this or even have need for it.