this post was submitted on 19 Sep 2024
20 points (100.0% liked)

KDE

5322 readers
106 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
 

I know how to do it in the battery section through the GUI, but I'd like to set it up through a command, for automation purposes, and particularly for KDE Connect commands.

you are viewing a single comment's thread
view the rest of the comments
[–] jpetso@lemmy.kde.social 3 points 1 month ago (1 children)

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.

[–] unknowing8343@discuss.tchncs.de 2 points 1 month ago (1 children)

What should I put in the <command> part?

[–] jpetso@lemmy.kde.social 1 points 1 month ago* (last edited 1 month ago) (2 children)

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.

[–] unknowing8343@discuss.tchncs.de 1 points 1 month ago

Aaaah, that's probably what Plasma is doing.

[–] SoulKaribou@lemmy.ml 1 points 1 month ago (1 children)
[–] jpetso@lemmy.kde.social 2 points 1 month ago

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.