Systemd-inhibit doesn't work, even with logind.conf set

ziphem · 10-18-2018, 12:04 AM

I know this is not a particularly new problem, but I've tried to understand this and haven't been able to figure it out. I'm on Fedora 28.

I edited /etc/systemd/logind.conf and made LidSwitchIgnoreInhibited=no.

I reboot. When I run

Code:

systemd-inhibit --why="Prevent sleep" --mode=block --what=handle-lid-switch

and I close the lid of my laptop, it sleeps nonetheless.

I'm seeing the below, too:

Code:

    What: handle-lid-switch
     Why: Multiple displays attached
    Mode: block

I'd appreciate any guidance on this. Thanks!

syg00 · 10-18-2018, 02:25 AM

What's wrong with setting the switch to ignore (in logind) ?.

Quote:

systemd-inhibit may be used to execute a program with a shutdown, sleep, or idle inhibitor lock taken. The lock will be acquired before the specified command line is executed and released afterwards.

With no command, the fd would reasonably be considered as released immediately.

Working as designed.

ziphem · 10-18-2018, 03:00 AM

Hi, thanks for the quick response. I wanted to suspend the sleep when running one certain program, which is why I didn't want to disable in logind.conf. I've tried also with a command, and this also did not inhibit suspend.

Code:

systemd-inhibit --what=handle-lid-switch --why="Prevent Sleep" --mode=block /home/me/GUI.py &

syg00 · 10-18-2018, 04:50 AM

I've never looked at this, but I can't imagine how that would work - try daemonising your code.

ziphem · 11-11-2018, 11:05 AM

Thanks. Even when I run in terminal something like systemd-inhibit --what=handle-lid-switch --who="Me" --why="On lid close" --mode=block sleep 59s, and I close the lid, it sleeps, and it should not - particularly considering that I've checked systemd-inhibit after running the command and I see that added as a listed inhibitor.