This is a discussion topic for the following Common Issue:
You can discuss the problem and its solutions here, but please note that debugging and technical feedback should primarily go to the issue trackers (e.g. Bugzilla) linked in the Common Issue, because that’s the place that developers watch, not here.
If there are any updates/changes/amendments for the Common Issue description, which you believe should be performed, please post it here.
Should we also point out the issue with virtual machines?
As far as I can see, at least with GNOME Boxes and virt-manager (I think they use the same engine underneath the hood), if the system eventually suspends, it doesn’t wake up forcing you to an hard reset or forced shutdown.
Not that I’m sure I would call it a Fedora problem, but screen blanking or suspending being enabled by default for a guest virtual machine is probably not the most desirable configuration.
The VM issue is already solved, just the update needs pushing stable:
https://bugzilla.redhat.com/show_bug.cgi?id=2180047
Would this be a default on all Fedora flavours? Not sure this is most sensible default for AC powered setups as it would prevent remote access (xdp, ssh).
Yes, this will be the default behavior as it seems to be needed to meet some energy saving compliance in various countries. However, you can easily disable this manually in Settings.
This is a good question, Marko. I added the following explanation to the issue description:
Note: Fedora Server ships a configuration override, which defaults to not suspending on AC power by default. In all other Fedora editions, the described configuration change should apply, as long as you have GNOME environment running.
So if it’s not clear, it shouldn’t affect KDE, XFCE, etc, if they don’t use gnome-settings-daemon (some spins like Cinnamon use it, I assume).
Thanks, yeah feels like for Server this should be off for sure. I’ll just have to apply this to to workstations then 
. Thanks for the help!
I think it’s a significant change as patch was removed and behaviour is different from <=F37, so would be worth calling it out and well documented as well.
It is quite easy to disable screen blanking for any fedora workstation (gnome) install by opening the control panel, privacy, and setting the blank screen timeout to ‘never’. I do this for all my VMs since I have the host set to blank its screen and it prevents interrupting what the VM may be doing.
Since screen blanking/locking is the default config it is up to the user to set each machine as they may choose.
I have to agree that it may not be the best choice for default, and maybe a selection during the initial setup would be better.
I agree, this behaviour caught me by surprise when upgrading from F37 to F38. When I went to log into the machine by SSH or open up podman hosted micro webservers, nothing was responding anymore.
For context, I run Fedora workstation as a hobbyist programmer and didn’t think I needed to use the server spin to have my machine remotely accessible at any time.
To be clear, you don’t need to. That’s just the default. I think it really is a good default. I have machines I want to be able to connect to remotely, or which keep running for some purpose, but others that don’t, and there’s really no good reason for them to be using energy. Wake-up with modern computers is really fast and reliable, so I think it really does make sense for most systems out-of-the-box. It’s easy to change if you have a specific reason to keep the system up.
For each release cycle, what tests related to Power Management is in the scope? Are they blocking? Are there PM test days planned? How to get involved?
PM issues are very hardware specific. Even wake up is not always working.
I think people can have different opinions here, but hope we can make this easier to manage as Power Settings as per user and what threw me off was new timeout for GDM session on the login screen 
. It would be awesome if that can be managed from the same section as user settings. Thanks for the good work and new release!
Marko, what is a way to change the default behavior, ie. prevent suspension or at least make the time-out period some huge number?
TIA
You cna disable or increase the timeout following the original post: GNOME suspends after 15 minutes of user inactivity, even on AC power
I just came here after running into the problem of being unable to ssh into my fedora workstation after upgrading 37 → 38. I’m running mate, and so was unable to find any settings option relevant to this in my gui, because it isn’t there in mate…
Mate “Control Center” > “Power Management” > “On AC Power” > “Put computer to sleep when inactive for…”
My use case is similar. My Fedora Workstation lives in an outbuilding, but I often use ssh from a laptop. Fortunately, the workstation supports wake-on-lan (install “wol” for Fedora, other distros use other names).
It turns out the my issue was in power management. I was lead astray by the fact that ssh failed causing me to think the the network was suspended when, in fact, the entire system was suspended. You can see the entire thread here: [SOLVED] Networking closes when users not logged in...
