I have a dell g3 laptop with a nvidia 1060 dgpu. I use both the builtin full hd display and a samsung 4k screen attached to the hdmi port.
I have set up my displays to use the "join displays" mode and i have selected the 4k display as my primary display. If the displays goes to sleep and i wakes them up then only the laptop display wakes up. To work around this i can open the display settings om that display and select mirror mode and this wakes up the screen connected to the hdmi port and when i revert this it stays awake.
I have the same issue if i reboot the laptop, the login window is not visible on the laptop display and the attached display flashes and goes back to sleep. But i can type the username and password to log in. After that i can use the "mirror" workaround to wake up the secondary monitor.
To be able to lock my screen without to have the screens put to sleep i use the "unblank lock screen extension" as a workaround.
Right now a have pop!_os 20.04 installed but this has been an issue with previous versions as well.
I have a dell g3 laptop with a nvidia 1060 dgpu. I use both the builtin full hd display and a samsung 4k screen attached to the hdmi port.
I have set up my displays to use the "join displays" mode and i have selected the 4k display as my primary display. If the displays goes to sleep and i wakes them up then only the laptop display wakes up. To work around this i can open the display settings om that display and select mirror mode and this wakes up the screen connected to the hdmi port and when i revert this it stays awake.
I have the same issue if i reboot the laptop, the login window is not visible on the laptop display and the attached display flashes and goes back to sleep. But i can type the username and password to log in. After that i can use the "mirror" workaround to wake up the secondary monitor.
To be able to lock my screen without to have the screens put to sleep i use the "unblank lock screen extension" as a workaround.
Right now a have pop!_os 20.04 installed but this has been an issue with previous versions as well.