From fd20fb257668bd28ea6800eca8cc1edd6966ec27 Mon Sep 17 00:00:00 2001 From: Marty Oehme Date: Wed, 21 Dec 2022 10:34:30 +0100 Subject: [PATCH] wayland: Fix automatic system suspend Previously, swayidle would wait for each command to be finished before executing the next which, with lockscreen running in the foreground, would not happen until it was unlocked again. The results were a working lockscreen after the timeout, but nothing else happening and suspend mode only being engaged *as soon as* the lockscreen was disabled (i.e. when you want to use the PC again). This removes swayidle's waiting for commands to finish and instead simply go on to the next timeout when the time is right and should thus fix the issue. --- wayland/.config/river/init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wayland/.config/river/init b/wayland/.config/river/init index 597058c..81ec6b6 100755 --- a/wayland/.config/river/init +++ b/wayland/.config/river/init @@ -249,7 +249,7 @@ exec kanshi & # start screen idle locking/dimming/sleep tool killall swayidle -exec swayidle -w \ +exec swayidle \ timeout "${time_to_lockscreen}" 'lockscreen' \ timeout "${time_to_screendim}" 'wlopm --off "*"' \ timeout "${time_to_suspend}" 'systemctl suspend-then-hibernate' \