Often after unlocking a previously locked session, my screen stays at 30% brightness. I'm not entirely sure whether this only happens after manual or automatic locking as it doesn't happen consistently.
More rarely, but still noticeably often, the screen stays completely off. I'm reasonably convinced that this is due to sway not receiving or not reacting to the output '*' dpms on message, as I can turn the screen back on by manually sending a swaymsg from another tty:
- Switch to different tty (screen turns back on).
- Log in and run
sleep 10; swaymsg -s "${XDG_RUNTIME_DIR}/sway-ipc.$(id -u)."*".sock" output '*' dpms on.
- Switch back to original tty (screen turns back off) and wait for screen to turn on.
Often after unlocking a previously locked session, my screen stays at 30% brightness. I'm not entirely sure whether this only happens after manual or automatic locking as it doesn't happen consistently.
More rarely, but still noticeably often, the screen stays completely off. I'm reasonably convinced that this is due to sway not receiving or not reacting to the
output '*' dpms onmessage, as I can turn the screen back on by manually sending a swaymsg from another tty:sleep 10; swaymsg -s "${XDG_RUNTIME_DIR}/sway-ipc.$(id -u)."*".sock" output '*' dpms on.