Thank you Darren, this is exactly my experience and seems relate to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2127853.
Gnome (Wayland) silently refuses to suspend, and gives no warning or visual clue as to why. The only simple way to suspend is therefore to start closing apps - inconvenient if the inhibitor app is the last one you close, you might as well shutdown your computer at that point rather than suspend. The apps that seem to be currently inhibiting suspend are browsers (e.g. Chrome, Firefox), music apps (e.g. Spotify, Rhythmbox ), video playback in apps or browsers (e.g. YouTube), social media pages with auto load posts (e.g. Twitter/Mastodon), and, crucially, Gnome Files (Nautilus) even when it has finished an operation (e.g. moving, copying, downloading). "sudo systemctl suspend -i" does work, but this is inconvenient, because it involves popping open a terminal, entering the command, and typing in the user password. Not ideal for GUI-oriented users. As a workaround, until this bug is resolved, I did two things: 1) I added "AllowInhibitors=yes" to "/etc/systemd/logind.conf", to allow me the user, as a non-root user, to suspend and control inhibitors without using sudo privileges. 2) I created a custom keyboard shortcut "CTRL+ALT+S" with the command "systemctl suspend -i", to be able to suspend without using the command line and without entering my password. Note that this workaround does not allow me to suspend using the GUI Gnome power menu, since this actions "systemctl suspend" and not "systemctl suspend -i", meaning that if there are inhibitors, it won't suspend. The "-i" is needed to ignore any inhibitors, but is not included in the GUI suspend button press. None of this is ideal from a UX perspective. When you press a GUI button, you either expect something to happen, or a warning to appear telling you why the system won't do what you have asked. From another perspective, why are all of these apps now suddenly setting inhibitors? I understand that you might want to save a document in LibreOffice because, if you suspend and then your laptop runs out of battery, then you have lost your work. But, listening to Spotify, if you are in the middle of a song when you suspend, the worst that can happen is you have to play the song from the beginning again. As for Gnome Files, if there is no visual clue as to an ongoing process, why is the inhibitor still set? Is the problem that Files is setting the inhibitor because something is being copied, but then doesn't release the inhibitor when the copying is finished? Finally, my workaround isn't ideal either, for two reasons: 1) It's a hack. 2) I might end up suspending, running out of battery, and losing my work, if I am not religious about saving it or checking whether important processes are finished. I am hoping this change in Gnome with Wayland will be ironed out for Gnome 50! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2130754 Title: Suspend is randomly inhibited in 25.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/2130754/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
