KDED6(8)

💖 KDED6 💖

okay bestie, so kded6 is the KDE daemon — and its whole thing is triggering Sycoca database updates when needed. That's the vibe. That's the job. 👑

---

✨ SYNOPSIS ✨

kded6 [--check]

---

🌸 DESCRIPTION 🌸

kded6 is literally the girl who consolidates several small services into one single process. Most of those are D-Bus services handed to her by KDED modules, but she also manages sycoca (which is a binary cache of servicetypes, MIME types and services used by KService) plus KConfig update scripts, whenever they're needed. multitasking queen 💅

For sycoca, she keeps an eye on the directories that hold .desktop files. The second a file gets added or removed, she waits 5 seconds (just in case it's a whole series of updates coming in, like okay let's not be dramatic), and then she launches kbuildsycoca6 to update the sycoca. patient but decisive ✨

For KConfig, she checks the newly-installed update files — yes, those *.upd files, the ones used to update users' configuration files when the configuration file formats change — and she runs the KConfig update utility to actually perform those updates. 🎀

And those same tasks also get run when kded6 is started, just to make sure the user configuration is up to date. no stale configs in this house 🙈

Real talk: you do not normally need to run kded6 directly. Plasma desktop sessions run it automatically, and it gets started on demand when an application tries to use a D-Bus interface that's provided by it or by one of its modules. she shows up when she's needed, main character energy fr fr 💖

---

🦋 OPTIONS 🦋

• --check — check the sycoca database, update it if necessary, and then exit. in and out, no small talk 💅

---

🌈 CONFIGURATION 🌈

kded6 can be configured with the kded5rc ini-style configuration file. On UNIX® systems, you'll find it at $XDG_CONFIG_HOME/kded5rc — and if $XDG_CONFIG_HOME isn't set, it defaults to ~/.config/kded5rc. iykyk 🫶

Configuration file entries are read on-demand, so you can make changes while kded6 is running. slay. However, all the current configuration options only really affect the startup behaviour of kded6. that's just the tea 🍓

⭐ The [General] section ⭐

Here's what lives in there:

• CheckSycoca — whether to update sycoca at startup (default: true).
• CheckUpdates — whether to perform outstanding KConfig updates at startup (default: true).
• DelayedCheck — whether to delay the initial sycoca update until about a minute after starting (default: false).

---

Each module also gets its own [Module-name] section in kded5rc, where name is the name of the module's desktop file without the .desktop extension. Inside it there's an autoload option that specifies whether the module should be automatically loaded when kded6 is started (default: false). 🌸

Heads up bestie: that setting can also be changed via kded6's D-Bus interface. two ways to do the same thing, iconic honestly 💜

---

👑 SEE ALSO 👑

kbuildsycoca6(8),

---

💀 BUGS 💀

Please use KDE's bugtracker[1] to report bugs. don't be shy, they wanna hear it 😭

---

🎀 AUTHORS 🎀

• David Faure <faure@kde.org> — Maintainer
• Waldo Bastian <bastian@kde.org> — Original author

---

🧚 NOTES 🧚

1. KDE's bugtracker https://bugs.kde.org

---

and that's the whole page, bestie 💖 this was KDE Frameworks, Frameworks 6, dated 2023-06-22, from the KDED6(8) manual. go forth and let the daemon do her thing ✨🦋