Open marcmerlin opened 2 years ago
Hi @marcmerlin , a lot has changed since 2014, I suggest you to read the systemd's take over of inhibit handling, but before you start coding look at the manpage of systemd-inhibit(1) instead.
Not everyone uses systemd.
Not everyone uses systemd.
I know, but sadly the hostile take over of responsibilities by systemd causes the drop of support for the previous alternatives and they become stale and buggy over time. I know that Gnome has its own inhibit API too that is mentioned at the bottom of the https://www.freedesktop.org/wiki/Software/systemd/inhibit/ page I linked before, the equivalent set of instructions would be https://sleeplessbeastie.eu/2022/01/31/how-to-identify-a-gnome-application-that-acquired-an-inhibitor-lock/ and for KDE it appears someone developed a plasma applet https://store.kde.org/p/1426768
Thanks @jnerin , don't love it, but I have systemd.
By the way systemd-inhibit(1) does the opposite of what I need. It prevents going to sleep, when I already have programs like chrome that do that against my will, and my laptop will never go to idle and start screensaver anymore :(
systemd-inhibit --list
--list
Lists all active inhibition locks instead of acquiring one.