jpetso

joined 9 months ago
[–] jpetso@lemmy.kde.social 1 points 1 month ago

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

[–] 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.

[–] jpetso@lemmy.kde.social 6 points 1 month ago

Ubuntu itself is based on Debian, so in a way you were still right :)

[–] jpetso@lemmy.kde.social 8 points 1 month ago (2 children)
[–] jpetso@lemmy.kde.social 1 points 2 months ago* (last edited 2 months ago) (3 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.

[–] jpetso@lemmy.kde.social 3 points 2 months ago (5 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.

29
submitted 2 months ago* (last edited 2 months ago) by jpetso@lemmy.kde.social to c/kde@lemmy.kde.social
 

About selected PowerDevil work in Plasma 6.2 and brightness controls in particular.