When a command is assigned a shortcut via System Setting / Shortcuts / Custom Shortcuts, the output of the command (stdout as well as stderr) is written to the syslog/journal with the identifier “kded5” when the shortcut is pressed. This behavior might be unexpected and therefore might lead to a spammed journal or confidential information ending up in the journal. (In my case I bound a script dealing with the clipboard to a hotkey. For debugging purposes (when not used via hotkey), the script prints the clipboard contents before processing. When accidentally pressing the hotkey with confidential clipboard contents, this unintentionally ends up in the journal.) Operating System: Arch Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.1-arch1-1 (64-bit) Graphics Platform: X11 PS: I was rather unsure about the correct product/component. Feel free to move.
As announced in https://pointieststick.com/2023/07/26/what-we-plan-to-remove-in-plasma-6/ and https://community.kde.org/Plasma/Plasma_6#Removals, I'm afraid KHotKeys has reached end-of-life in Plasma 6. Accordingly, all bug reports and feature requests for it must be closed now. Most of what KHotKeys could do can already be done with the newer KGlobalAccel system in Plasma 6. A few features such as mouse gestures and triggering conditions based on changes to window states are not yet implemented in the new system. These will be added in the future if and when resources materialize for them, and/or when a kind soul submits patches to implement them! :) Meanwhile, the 3rd-party "Mouse Actions" app (https://github.com/jersou/mouse-actions) may be usable for implementing your own mouse gestures again. Thanks for your understanding, everyone.