KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
KDE 6 seems to have gotten rid of run command, mark taskbar entry and log to a file options in applications specific settings under notification settings, only play a sound and show message in popup actions remain.
Are there any plans to bring back this functionality in future updates?
What I want is not (just) that the screen turns off when the lock timer times out, but that I can push 'lock' or a key combination and have the system lock and the screen turn off immediately.
The new 'when locked, turn off screen' setting should help with this, but setting it too low will presumably make it hard to unlock.
For running backups, 'after a period of inactivity' could help.
It still seems like the removal of a useful feature.
This might be a problem, I don't think you can have both behaviors at the same time.
Setting it to 0 will function just how you described, it won't make unlocking it harder. When the password prompt is open, it blocks the screen off behavior.
It should work for your case of creating backups when idle. inactivity = no user input or program sending block signal = most likely idle.
Sure, but for your case I don't believe you actually need it.
The screen turning off when it automatically locks is an added bonus; the priority is to be able to command the system to simultaneously lock and turn off the screen. You're correct that the setting at zero seconds safely achieves that.
I've had other, more stupid uses for running commands, though I don't think any are actively in use.
Taking actions on network reconfiguration, charge completion, and SMART failure are all things that spring to mind. It's nice to be able to set those kinds of things in a GUI rather than putting them in /etc/something.d