#1 2015-12-18 22:43:15

dshort

New Member

Registered: 2015-12-18

Posts: 1

some (not all) web sites prevent hibernation when open in browser

I have a weird problem and no idea how to solve it. When some websites are open in a browser (chromium or iceweasel), they prevent the system from hibernating. I've only seen this happen with gmail open (logged in or logged out), but from googling around it seems like this happens to other people with other websites. I haven't seen a post about this here, and none of the solutions I've seen elsewhere have helped. Here's the reproducible behavior I have:

Open gmail tab
Open terminal, do

systemctl hybrid-sleep

or

systemctl hibernate

and I get:

Failed to put system into <state> via logind: sleep verb not supported

where <state> is "hybrid sleep" or "hibernate"

This happens with the gmail tab open regardless of whether or not I'm logged in. If I close the tab I can hibernate as normal. If I walk away from the computer for a long time (with the tab open) and come back, the screen has locked but when I log in there's a popup in the system tray that gives an error mentioning power manager and "sleep verb not supported."

This is a big problem for me as I'm on a laptop. I've had the battery run down to where the system can't boot without being plugged in twice now. That'll kill the battery, I can't afford a new one, and I can't be sure I'll remember to close my email every time I leave the system.

Does anyone have a fix for this?

Last edited by dshort (2015-12-18 22:43:34)

ohnonot

...again

Registered: 2015-09-29

Posts: 5,592

Re: some (not all) web sites prevent hibernation when open in browser

i guess in the end you have to find out what these websites do that keeps the system alive.
ultimately, the system goes to sleep when it's inactive.
obviously, the websites are doing something that is considered activity.

one thread suggests it has to do with swap (makes sense to me - browser cache, .js constantly reloading...)

maybe you can tweak the browser (should be possible with iceweasel/firefox) to do something about it.
maybe you can use the noscript addon to prevent java script execution on those critical (or all) web pages.

or maybe you can tell systemd to consider only direct user input as activity, but this might endanger other critical processes.

anyhow, here's my search. the first few results seem dead ends, but further down is more interesting stuff. bug reports, github issues...