dotfiles/home/.config/systemd/user/systemd-lock-handler-swaylock.service
ItsDrike 1f8bebd13b
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.
2022-11-20 03:15:58 +01:00

19 lines
530 B
Desktop File

[Unit]
Description=Run Swaylock screenlocker on lock dbus event (using systemd-lock-handler)
# if swaylock exists cleanly, unlock this session
OnSuccess=unlock.target
# When lock.target is stopped, stop this too
PartOf=lock.target
# Delay lock.target until this service is ready
After=lock.target
[Service]
# systemd will consider this service started when swaylock forks
# which swaylock will only do after it has locked the screen
Type=forking
ExecStart=/usr/bin/swaylock -fF
Restart=on-failure
[Install]
WantedBy=lock.target