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.
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.
Also, preceding the Goals session, Kevin Ottens is conducting a KDE stack training session! Starts in just over an hour: https://floss.social/@kde/113276942214195123
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.
Ubuntu itself is based on Debian, so in a way you were still right :)
Found this on Reddit, hopefully it helps: https://www.reddit.com/r/kde/comments/1g0lpb9/comment/lrd4t1k/
Anything that runs as long as you want the block to be. Usually
sleepis a good one, usesleep infinityif you want the blocker to never go away until thesystemd-inhibitprocess is killed manually.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.