Post #3443357

2026-06-28 07:36 UTC

Modern DE ≠ unnecessary metadata-collecting services which you can not control within the DE interface. I do not want a “minimal” environment, I want one that looks pretty and is adjusted straightforwardly. Background metadata syncing has nothing to do with graphical environment. I understand that KDE is a whole ecosystem, but a service like this, shipping together with the DE, unreachable through normal settings interface is not what I’m expecting from a DE. Especially from such a modern and featurefull one. If I wanted to manage my DE with text configs, I would go for hyprland or something like this. It’s the issue with KDE that it doesn’t implement accessible configuration options for certain components. Hereby I’m not saying that KDE is totally bad. My main complaint isn’t the existence of Akonadi by itself, some people I’ll hardly ever meet in person would find it’s functionality extremely useful for a reason. But the fact it is uncontrollable with any KDE settings is dissapointing. The actual magic of Linux here is that I can still find a text config and disable anything I don’t need there. Without ditching a whole DE because of a couple of things I don’t like. PS. I have never been on reddit.

Replies (3)

@Hund@feddit.nu 2026-06-28 08:34

It’s using your data locally on your machine. If you don’t trust one of the biggest open source projects in the community, perhaps computers is not your thing. :D

Open ##3444517
@Shimitar@downonthestreet.eu 2026-06-28 08:47

So what’s the point? A modern and fully integrated de uses background services and those services are required for many pieces to work so much that they have made not that easy to disable the service? If that’s the point, you are definitely being unreasonable. On the other hand the service can still be disabled understandably by text file editing to prevent users from breaking their system. I find the lack of an UI setting to disable it a reasonable choice, and yourself are telling me that it’s still removable by user anyway. A power user indeed, but still user manageable. Plasma user base definitely is not the customize everything people. I think it’s reasonable that akonadi needs deeper user action to be disabled That service is local only and needed for many apps to work, including stock widgets. What is your point against akonadi exactly? I would complain about that search indexer daemon (kglobalaccel or something similar) in plasma that still after years sometimes gobbles up 100% on a CPU core after screen unlock instead … But whatever

Open ##3444756
@Mordikan@kbin.earth 2026-06-28 15:44

So, really the issue is you expect KDE to present it in UI which is not the case. You would have to use the control binary to stop it from running (akonadictl stop). To prevent it from running in the future, you'd have to edit/create it's configuration in $HOME/.config and add something like StartServer=false to [General]. There is no way to do this in the UI.

Open ##3450954