I'm using swayidle/swaylock on two different machines, one with intel cpu and gpu, and the other with amd cpu and nvidia gpu, and I'm using them with two different sets of monitors, in one case I have two Lenovo Thinkvision monitors, and in the other, a TCL tv/monitor, both with roughly the same config.
On both machines, if I walk away and come back, the screen doesn't always turn back on. When this happens, I can usually work around the problem by switching to the virtual terminal where gdm is running, and come back again.
I'm using swayidle/swaylock on two different machines, one with intel cpu and gpu, and the other with amd cpu and nvidia gpu, and I'm using them with two different sets of monitors, in one case I have two Lenovo Thinkvision monitors, and in the other, a TCL tv/monitor, both with roughly the same config.
On both machines, if I walk away and come back, the screen doesn't always turn back on. When this happens, I can usually work around the problem by switching to the virtual terminal where gdm is running, and come back again.
I'm using this script to run swayidle:
This is the log I see around the sleep event, and later waking it up.