Move to systemd-lock-handler instead of swayidle for locking

Swayidle will likely end up dropping logind support, and they themselves
describe it as unstable. For this reason, move to the suggested
alternative: systemd-lock-handler, and just have swayidle run the
command to trigger the logind session lock event, picked up by
systemd-lock-handler.

See <https://github.com/swaywm/swayidle/issues/117> for reference.
This commit is contained in:
ItsDrike 2022-11-20 02:48:19 +01:00
parent 89a5b15bbd
commit 1f8bebd13b
No known key found for this signature in database
GPG key ID: B014E761034AF742
4 changed files with 20 additions and 2 deletions

View file

@ -1,4 +1,2 @@
timeout 300 "hyprctl dispatch dpms off && dunstctl set-paused true" resume "hyprctl dispatch dpms on && dunstctl set-paused false"
timeout 310 "loginctl lock-session"
before-sleep swaylock -fF
lock swaylock -fF