with swaylock, when the system is suspended by systemd the screen turns on after resuming and receiving some input and allows the user to see the lock screen before letting the user back into the system.
But with swaylock-effects, the system resumes from sleep and the screen won't come back on until after it is unlocked meaning the user can't see anything and has to type the password into a black screen and hope for the best.
Switching to a different TTY will turn on the screen but switching back will turn it off again.
The after-resume command is not needed with vanilla swaylock and it doesn't help with swaylock-effects
Expected behavior:
with swaylock, when the system is suspended by systemd the screen turns on after resuming and receiving some input and allows the user to see the lock screen before letting the user back into the system.
swaylock:
Issue:
But with swaylock-effects, the system resumes from sleep and the screen won't come back on until after it is unlocked meaning the user can't see anything and has to type the password into a black screen and hope for the best.
Switching to a different TTY will turn on the screen but switching back will turn it off again.
The after-resume command is not needed with vanilla swaylock and it doesn't help with swaylock-effects
swaylock-effects: