I cannot seem to enable automatic suspend, the menu is not there (see screenshot), it was there before IIRC, and I set it to 15 min, but sometime in the last couple of weeks it disappeared. I did not remembered tinkering with any of the menu.
I tried using gsettings (via dconf and terminal), but it still won’t auto suspend.
gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 300
gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 120
My info:
OS: Fedora Linux 42 (Workstation Edition) x86_64
CPU: Intel(R) Core™ i5-5300U (4) @ 2.90 GHz
GPU: Intel HD Graphics 5500 @ 0.90 GHz [Integrated]
Question
Is there any way to enable the menu again so I can set it using GUI? Thank you.
because you have the system in power saving mode.
If you go back to the general tab and select either performance or balanced power modes, then this becaome available to configure.
weirdly enough, it came back like 2-3 minutes ago. But I don’t know if that’s because of power saving mode. Because I remembered switching back and forth performance-power saving yesterday when trying to solve the problem by doing that since 2 days ago, and I have been on performance since yesterday.
I was just uninstalling an extension - blur my shell, because it was outdated, but I also doubt that is the cause. Didn’t do anything else but watch youtube and uninstall that extension.
Thank you Jef!
----edit----
it came back again! the auto suspend is gone, its still in performance, and I close the power setting again, open it again, several time and at the last time its back again.
I was just opening extension (trying to install and uninstall blur my shell), watch youtube for 2 minutes.
Now the autosuspend option is back there again, and IDK what happen really.
I’ve been experiencing this as well on a AMD Ryzen AI 9 365 (Strix Point) laptop, latest kernel 6.18.5. Suspend configuration no GNOME settings comes and goes, for no apparent reason.
It looks like the whole thing will be undone (regression).
The worst I was reading about is:
In principle auto-suspend could stay enabled but just ask for a prompt when it wants to suspend?
The thing with auto-suspend is that the user is typically not in front of the computer when it happens, so that prompt is never going to get answered (and if an enterprise-scenario user is in front of the computer when it happens, then yeah, they’re going to be very confused).
If there has to be some enterprise-scenario then the options should just be grayed out, with the hover text available, that in enterprise environment the user can not manipulate this options. This should not affect a common home user which wants to decide how to use its device.
P.S.
I do have a installation of Rahwhide 45 there it just shows this:
I just want to say that right now on my F43 personal laptop I’m still able to get the “Automatic Suspend” delay options in the “power saving” tab as I expect. I can’t confirm your experience that something has gone missing. I havent had a chance to go back and do a fresh install to ground truth that I haven’t walked my system into different behavior somehow. Other than to say I always expect my system to be more wonky because I do wonky things with it.
Me to in F43. However I mentioned that the screenshot is from Rawhide 45. Till this is released there can change a lot.
When I need the computer to resolve a task without going to suspend I do need to be able to switch this option off. The rest of the time I am really happy with this function.
When I need the computer to resolve a task without going to suspend I do need to be able to switch this option off. The rest of the time I am really happy with this function.
If the issue is that after starting any inhibiting auto-suspend app (as reported upstream) the option disappears, then you’d reboot, go straight into settings and enable automatic suspend before any application causes it to bug itself out. When you have a task you want to keep the computer on you might want to use Caffeine for example. Or do it in the terminal or just reboot and enable it from the GUI again
