If I manually lock the laptop (via the bind CTRL+L, set to exec, pidof hyprlock || hyprlock) and wait for the timeout of hypridle to suspend (i.e. 15 min), then try to wake the laptop, I am greeted with a red screen. I switched to another tty, and tried to kill hyprlock, then hypridle, but the red screen was still there. No inputs were received by the session. Tried to run hyprlock via tty and ssh session, but it says no Wayland display detected.
hypridle.conf
general {
lock_cmd = pidof hyprlock || hyprlock # avoid starting multiple hyprlock instances.
unlock_cmd = pkill -USR1 hyprlock
before_sleep_cmd = loginctl lock-session # lock before suspend.
ignore_dbus_inhibit = false
after_sleep_cmd = hyprctl dispatch dpms on # to avoid having to press a key twice to turn on the display.
}
listener {
timeout = 150 # 2.5min.
on-timeout = brightnessctl -s set 10 # set monitor backlight to minimum, avoid 0 on OLED monitor.
on-resume = brightnessctl -r # monitor backlight restore.
}
listener {
timeout = 300 # 5min
on-timeout = loginctl lock-session # lock screen when timeout has passed
}
listener {
timeout = 330 # 5.5min
on-timeout = hyprctl dispatch dpms off # screen off when timeout has passed
on-resume = hyprctl dispatch dpms on # screen on when activity is detected after timeout has fired.
}
listener {
timeout = 900 # 15min
on-timeout = systemctl suspend # suspend pc
}
If I manually lock the laptop (via the bind CTRL+L, set to
exec, pidof hyprlock || hyprlock
) and wait for the timeout of hypridle to suspend (i.e. 15 min), then try to wake the laptop, I am greeted with a red screen. I switched to another tty, and tried to kill hyprlock, then hypridle, but the red screen was still there. No inputs were received by the session. Tried to run hyprlock via tty and ssh session, but it says no Wayland display detected.hypridle.conf