While my PC is on in Fedora 43 desktop, if I switch my monitor off and then back on again, my monitor never gets a signal back and eventually powers down. The only way I have found to resolve this is to turn the monitor on and press Ctrl+Alt+F1. This isn’t ideal as this makes me log back in and I deliberately turn off screen locking permanently in the settings. Any ideas why my monitor doesn’t get a signal in this scenario? This is Gnome specific because I tried Fedora 43 KDE and it is doesn’t happen in that DE.
But ctrl+alt+f1 seems to already be doing that. For the record, I didn’t know what ctrl+alt+f1 did - it was just a suggestion I found on the internet somewhere (I forget where now). So I turn my monitor off, turn it back on again, no signal. I then press ctrl+alt+f1 and it wakes my monitor up and immediately I see the graphical login screen and I can then enter my password and carry on.
I just looked up what ctrl+alt+f1 is supposed to do and it seems to be it takes you to a terminal screen. But this isn’t the case for me.
Edit: If I do press ctrl+alt+f1 and rather that login in that gui login screen I press ctrl+alt+f2 it does indeed just take me back to the screen as if I hadn’t turned my monitor off. That is still an inconvenience compared to just having to turn the monitor on.
f1 is the gdm screen
f2 is your gnome session if it’s still active.
so try again, switch to gdm wait for screen to appear and switch to f2 to see you gnome session.
suggestion: don’t turn off screen but use a timeout of 1 minute to put monitor into power-save state. You can use an extension like caffeine to keep monitor active.
Thanks for helping. It still feels like a workaround rather than a proper solution but better than nothing. It’s just this doesn’t happen on the same machine with either KDE or Windows.
On the surface it doesn’t seem like that big a deal but it seems to have other consequences. For example, the only way I can get the screen to come back on is by pressing ctrl+alt+f1. However, this disconnects my bluetooth headphones which then require me to manully reconnect them. It’s lots of little inconveniences like that which add up into making this quite annoying.
Adding some more info to this issue which is annoying me enough that I have tended to dual boot into Windows by default now.
On one occassion this morning when turning the monitor back on it did actually get a signal. However, this looked like a lock screen showing the time and date and then a message below saying something like click or press a key to login. Pressing the mouse or keyboard had no effect though and still required me to press ctrl+alt+f1. I assume this is still related in some way. Does it shed any light on the issue and how to fix it?
Also, if someone could actually explain what ctrl+alt+f1 does that would be great. I am doing it without even knowing what it does, why it works and if there are any potential downsides to doing it.