[Testing - Trixie] [Solved] Suspend broken, power button now prompts for shutdown

[jost-s]

Running GNOME on a desktop PC, suspend has been working reliably and was configured to be triggered by the power button out fo the box.

I don't know what I've changed or if it was some package upgrade, but more often than not suspend is broken. When I press the power button now, I'm prompted for a shutdown. When I select "Suspend" from the system menu, nothing happens.

`systemd-inhibit` outputs:

Code: Select all

$ systemd-inhibit 
WHO            UID  USER PID  COMM            WHAT                                                     WHY                                       MODE 
ModemManager   0    root 987  ModemManager    sleep                                                    ModemManager needs to reset devices       delay
NetworkManager 0    root 960  NetworkManager  sleep                                                    NetworkManager needs to turn off networks delay
UPower         0    root 1291 upowerd         sleep                                                    Pause device polling                      delay
GNOME Shell    1000 jost 1947 gnome-shell     sleep                                                    GNOME needs to lock the screen            delay
jost           1000 jost 2115 gsd-media-keys  handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses                 block
jost           1000 jost 2115 gsd-media-keys  sleep                                                    GNOME handling keypresses                 delay
jost           1000 jost 2117 gsd-power       sleep                                                    GNOME needs to lock the screen            delay
jost           1000 jost 1916 gnome-session-b sleep                                                    user session inhibited                    block

8 inhibitors listed.

After a restart suspend works from system menu as well as power button, but after using applications for a while, It stops working. I need to log out and then can suspend.

How can I diagnose what the issue is?

[sunrat]

Moved to Testing and Unstable

[jost-s]

I'm pretty sure now after some trying that it has to do with my browser. When suspend doesn't work and instead the shutdown prompt appears, I close the browser and suspend works as expected. Could it be some media playback that's inhibiting suspend and causing this weird behavior?

[jost-s]

Yes, that was the culprit. It's a particular website that streams video content. When its tab is open, I cannot suspend. Closing that tab enables suspending again. Is that intended behavior?

[FreewheelinFrank]

Yes, that was the culprit. It's a particular website that streams video content. When its tab is open, I cannot suspend. Closing that tab enables suspending again. Is that intended behavior?

I believe so: Firefox is asking Gnome not to lock or blank the screen or to suspend on the assumption that you are watching something, or the website contains a request not to lock/blank/suspend.

[jost-s]

Agreed. I doubt that It's intended to display the shutdown prompt instead. Also it's confusing that the browser doesn't show up under `systemd-inhibit`.

[FreewheelinFrank]

Agreed. I doubt that It's intended to display the shutdown prompt instead. Also it's confusing that the browser doesn't show up under `systemd-inhibit`.

I had a look for some documentation on how Firefox does this, but could not find anything definitive, so I'm just guessing here.

I suspect suspend is disabled along with blank and lock screen as part of the process of keeping the screen on while media is playing - an intended action. If the user opts to shutdown, then they obviously don't want to continue watching the media, and there would be no reason to block the request. I can only imagine there is no override process in the user-selected suspend option via the power button because nobody envisaged that the user might want to suspend while watching media.

I have seen reference to the following command. Is the output any different with the tab open?

Code: Select all

gnome-session-inhibit --list

https://forums.mozillazine.org/viewtopic.php?t=3126162

Could Firefox be using DBus and org.freedesktop.PowerManagement rather than Systemd?

https://bugzilla.mozilla.org/show_bug.cgi?id=1862159

Edit: format.

[jost-s]

Thanks for the investigation.

I suspect suspend is disabled along with blank and lock screen as part of the process of keeping the screen on while media is playing - an intended action. If the user opts to shutdown, then they obviously don't want to continue watching the media, and there would be no reason to block the request. I can only imagine there is no override process in the user-selected suspend option via the power button because nobody envisaged that the user might want to suspend while watching media.

I agree. I was surprised to see a shutdown from pressing the power button, because I learned that it was changed by the GNOME team to not being configurable for the power button.

The first link shows a 404 for me.

[FreewheelinFrank]

Sorry, it's a command not a link. Wrong tags used - corrected.

[jost-s]

Haha, I didn't figure that out!

Yes, that's showing the difference (with and without the tab open):

Code: Select all

~ $ gnome-session-inhibit --list
firefox-esr: video-playing (idle)
~ $ gnome-session-inhibit --list
No inhibitors

[jost-s]

If there's nothing wrong here, I'll consider this resolved.