summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
367a240)
xss-lock makes sure that i3lock is triggered when the session is locked
via systemd by other means than xidlehook, i.e. LidClose events.
Since there is now a handler for session locking in systemd, might as
well use that on the timer as well via lock-session.
xidlehook \
--socket=$XIDLEHOOK_SOCKET \
--not-when-fullscreen \
xidlehook \
--socket=$XIDLEHOOK_SOCKET \
--not-when-fullscreen \
- --timer 300 'xset dpms force off' '' \
- --timer 300 'i3lock -c 000000' '' \
- --timer 3600 'systemctl suspend' '' \
+ --timer 300 'xset dpms force off' '' \
+ --timer 300 'loginctl lock-session' '' \
+ --timer 3600 'systemctl suspend' '' \
&
elif [[ $(hostname) == "chronos" ]]; then
xidlehook \
--socket=$XIDLEHOOK_SOCKET \
--not-when-fullscreen \
&
elif [[ $(hostname) == "chronos" ]]; then
xidlehook \
--socket=$XIDLEHOOK_SOCKET \
--not-when-fullscreen \
- --timer 300 'xset dpms force off' '' \
- --timer 300 'i3lock -c 000000' '' \
- --timer 1800 'systemctl suspend' '' \
+ --timer 300 'xset dpms force off' '' \
+ --timer 300 'loginctl lock-session' '' \
+ --timer 1800 'systemctl suspend' '' \
&
elif [[ $(hostname) == "skull-canyon" ]]; then
xidlehook \
&
elif [[ $(hostname) == "skull-canyon" ]]; then
xidlehook \
--timer 300 'i3lock -c 000000' '' \
&
fi
--timer 300 'i3lock -c 000000' '' \
&
fi
+
+xss-lock -- i3lock --nofork --color=000000 &