There is kde-inhibit --screenSaver <command> provided by KDE.
But these days, I would just recommend everyone to use systemd-inhibit --what=idle --why=<because> --who=<myself> <command> instead. Works across desktops and does the same thing.
this post was submitted on 19 Sep 2024
20 points (100.0% liked)
KDE
5313 readers
115 users here now
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.
Plasma 6 Bugs
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.
founded 1 year ago
MODERATORS
What should I put in the <command> part?
Anything that runs as long as you want the block to be. Usually sleep is a good one, use sleep infinity if you want the blocker to never go away until the systemd-inhibit process is killed manually.
Aaaah, that's probably what Plasma is doing.
Would yes command work ?
Presumably, but it prints "y" to the program output as fast as your CPU allows it, so that's probably not a very efficient way to do it.
Not KDE but might be similar: For the MATE desktop it is mate-screensaver-command --inhibit. I would expect something similar for KDE.
I don't know if this fits your use case (you didn't describe what you want to achieve in detail), but commands that can possible help if the screen did lock (or turn off):
- Unlock the lockscreen:
loginctl unlock-screen - Turn on the screen:
kscreen-doctor --dpms on
Wasn't that. I want to keep the screen on. No sleep, no lockscreen, no blackscreen, etc.