Suspend or not to suspend

Everybody: Help! suspend isn’t working

Me: Help! Suspend _is_ working

So… today I noticed that I forgot something on my Fedora Workstation at home. No problem, we have Wireguard, no? So I asked a family member to start my computer at home, which they did, and I logged into my box via ssh.

After that I had to install a programm first before starting my work so I installed it via sudo. The dnf command succeeded and directly after that – to my _utter_ surprise – did the terminal print the message “The system is going into suspend NOW”.

And it was gone. Just like my family members, who left the building in the meantime. WoL didn’t succeed. Work delayed 🤷

I was flabbergasted. And I tried it again later at home. If I do not login via gdm… the system suspends on it’s own again!

What on earth is doing this and how can I stop this from happening again???

Update:

As mentioned in the comments this is a setting of Gnome but for the `gdm` user. “sudo -u gdm dbus-run-session gsettings list-recursively org.gnome.settings-daemon.plugins.power | grep sleep” list all options and removing the timeout should prevent this: “sudo -u gdm dbus-run-session gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0”

This crept back in during one of the last dist upgrades though and failed with a permission error on the not existing path “/var/lib/gdm/.config/dconf/”. I just created the folder and set it’s permission to readwrite for “gdm”. After that I could set the ac-timeout to 0 again.

https://beko.famkos.net/2024/05/08/suspend-or-not-to-suspend/ #gnome #JustLinuxThings #linux #Suspend