Method call time=1509049627.133691 sender=:1.260 -> destination= serial=3 path=/org/freedesktop/PowerManagement/Inhibit interface= member=Inhibit PowerManagemen t.Inhibit member=UnInhibit PowerManagemen t serial=4 path=/org/ freedesktop/ PowerManagement /Inhibit interface= org.freedesktop. If you close the tabs with WebRTC connections, in the dbus-monitor session you'll then see Chrome release the Inhibit and the screen will lock after the usual timeout: To see which tab or tabs are the culprits, go to chrome: //webrtc- internals/ and you should see each connection listed. The final line above gives the clue to why this is occurring: a tab has opened a WebRTC connection and Chrome thinks this is something interactive that needs to prevent screen lock/sleep. String "WebRTC has active PeerConnections" String "/usr/bin/ google- chrome- stable" PowerManagemen t serial=3 path=/org/ freedesktop/ PowerManagement /Inhibit interface= org.freedesktop. If you run `dbus-monitor -session`, then relaunch Chrome, you'll see it is inhibiting sleep: Just ran into this today also and found a solution. If it's a Chrome bug it must be using other mechanisms to prevent the idle timeout. No matter the inhibitor is present or not. The screen NEVER locks when this tab is open. This inhibitor seems to stay for 10-15 seconds, then goes away for another 30-60 seconds. The flags just inhibits suspend, not locking or entering powersaving mode. GetAppId: ('/usr/ bin/google- chrome- stable' ,) After these 70 seconds pass, the screen locks.Ħ) Regarding Chrome, this is the information I get when querying the inhibitor: GetFlagsĥ) When testing, I can inhibit for 70 seconds, idle timeout being 60 (1 minute). SessionManager -object-path /org/gnome/ SessionManager/ Inhibitor1686 -method org.gnome. Object path "/org/gnome/ SessionManager/ Inhibitor1686" GetInhibitorsme thod return time=1468170482. SessionManager /org/gnome/ SessionManager org.gnome. $ dbus-send -print-reply -dest= org.gnome. $ gnome-session- inhibit -app-id test -reason "manual idle inhibit" -inhibit-only -inhibit idle:suspend I can trigger it manually with:Ģ) Gnome screen saver never receives the "session idle" status callback.ģ) When Chrome is not running, I can manually inhibit the idle status: I'm pretty sure that Chrome is doing something else of what i've found out.ġ) Gnome screen saver works correctly. Many people find this problem when using Yahoo Mail.
The culprit seems to be that Chrome issues some suspend inhibitions through dbus when doing certain operations. com/DebuggingSc reenLocking# Debugging_ procedure I've followed the steps in https:/ /wiki.ubuntu. The screen never shuts down unless I manually lock the session with CTRL-ALT-L. I've been having this issue sice before 14.04, which I recently upgraded (fresh install) to 16.04.Īfter fresh install, the screen would turn down and lock the computer after 10 minutes (or whatever time I setup).
The screen should lock after the configured timeout in settings. The screen doesn't lock when having certain pages in Chrome tabs com/ubuntu xenial-updates/main amd64 Packagesĥ00 es.archive.
0 kommentar(er)
