Just ran into this today also and found a solution. If you run `dbus- monitor --session`, then relaunch Chrome, you'll see it is inhibiting sleep:
method call time=1509049627.133691 sender=:1.260 -> destination=org.freedesktop.PowerManagement serial=3 path=/org/freedesktop/PowerManagement/Inhibit; interface=org.freedesktop.PowerManagement.Inhibit; member=Inhibit string "/usr/bin/google-chrome-stable" string "WebRTC has active PeerConnections" 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. To see which tab or tabs are the culprits, go to chrome://webrtc-internals/ and you should see each connection listed. 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: method call time=1509049693.689398 sender=:1.260 -> destination=org.freedesktop.PowerManagement serial=4 path=/org/freedesktop/PowerManagement/Inhibit; interface=org.freedesktop.PowerManagement.Inhibit; member=UnInhibit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600622 Title: Screen doesn't lock or go to sleep when certain Chrome tabs are open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
