Screen doesn't lock or go to sleep when certain Chrome tabs are open
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-session (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy gnome-session-bin
gnome-session-bin:
Installed: 3.18.1.
Candidate: 3.18.1.
Version table:
*** 3.18.1.
500 http://
100 /var/lib/
3.
500 http://
I'm using gnome-session-
What happens:
The screen doesn't lock when having certain pages in Chrome tabs
Expected:
The screen should lock after the configured timeout in settings.
I've been having this issue sice before 14.04, which I recently upgraded (fresh install) to 16.04.
After fresh install, the screen would turn down and lock the computer after 10 minutes (or whatever time I setup). At one point it stopped working. The screen never shuts down unless I manually lock the session with CTRL-ALT-L.
I've followed the steps in https:/
The culprit seems to be that Chrome issues some suspend inhibitions through dbus when doing certain operations. Many people find this problem when using Yahoo Mail. I can reproduce it with Odoo. I'm pretty sure that Chrome is doing something else of what i've found out.
1) Gnome screen saver works correctly. I can trigger it manually with:
$ gnome-screensav
2) Gnome screen saver never receives the "session idle" status callback.
3) When Chrome is not running, I can manually inhibit the idle status:
$ gnome-session-
Inhibiting until Ctrl+C is pressed...
4) I can query the inhibitors:
$ dbus-send --print-reply --dest=
array [
object path "/org/gnome/
]
$ gdbus call --session --dest org.gnome.
('test',)
$ gdbus call --session --dest org.gnome.
('manual idle inhibit',)
$ gdbus call --session --dest org.gnome.
(uint32 12,)
12=4(suspend) + 8(idle)
5) When testing, I can inhibit for 70 seconds, idle timeout being 60 (1 minute). After these 70 seconds pass, the screen locks.
6) Regarding Chrome, this is the information I get when querying the inhibitor:
GetAppId: ('/usr/
GetReason: ('Uploading data to 10.200.0.163',)
GetFlags: (uint32 4,)
The flags just inhibits suspend, not locking or entering powersaving mode.
This inhibitor seems to stay for 10-15 seconds, then goes away for another 30-60 seconds. The screen NEVER locks when this tab is open. No matter the inhibitor is present or not.
I'm not sure where to go on. If it's a Chrome bug it must be using other mechanisms to prevent the idle timeout. Any ideas on what to look for?
Julian.
Changed in gnome-session (Ubuntu): | |
importance: | Undecided → Low |
description: | updated |
I have exactly the same problem on Ubuntu 16.04. If Google Chrome is running and toggl, twitter, or gmail tab is opened than the screen lock doesn't work. The only workaround is to press CTRL-ALT-L or close Google Chrome.