Issue metadata
Sign in to add a comment
|
Chromebox does not suspend/lock-screen when idle and logged in
Reported by
john.stu...@linaro.org,
May 4 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10452.74.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.137 Safari/537.36 Platform: 10452.74.0 (Official Build) stable-channel panther Steps to reproduce the problem: 1. Boot and log into chromebox 2. Walk away for a few hours 3. Come back, see chromebox screen still on and logged in 4. Hit sleep button on my keyboard to lock the screen 5. Walk away 6. See system does correctly suspend when not logged in. What is the expected behavior? Chromebox to sleep after some idle time, propmpting for password when you return. What went wrong? I think I first started seeing this in Chrome 65, where a number of display related issues cropped up (2x display scaling broke w/ my 4k screen until I enabled the new display scaling flag, and mouse-cursor scaling stopped working consistently as well) Again, when locking the screen manually, it does go back into suspend as one expects. I just wish it would do it automatically as it used to. I suspect logic for laptops where devices might not go to sleep while a external monitor is plugged in (like during a presentation) is tripping this up, as we always have external monitors on chromeboxes. Did this work before? Yes ChromeOS 64 (I think) Chrome version: 66.0.3359.137 Channel: stable OS Version: 10452.74.0 Flash Version: 29.0.0.140 /opt/google/chrome/pepper/libpepflashplayer.so
,
Aug 15
Still seeing this with Chrome 68 on my system. User Agent: Mozilla/5.0 (X11; CrOS x86_64 10718.71.2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.87 Safari/537.36 Platform: 10718.71.2 (Official Build) stable-channel panther Firmware: Google_Panther.4920.24.26
,
Aug 15
Oddly, I've just noticed I'm seeing this w/ my Chromebook pro as well when the device is unplugged and no monitors are attached. Version 68.0.3440.87 (Official Build) (64-bit) Platform: 10718.71.2 (Official Build) stable-channel caroline Firmware: Google_Caroline.7820.356.0 I am not using any extensions that block suspend (that I am aware of).
,
Aug 15
Disabled all extensions and removed my yubikey to make sure that wasn't somehow preventing suspend, and I'm still seeing the problem on my Chromebook Pro. I'm starting to wonder if this is due to something in my company's administrator policy. Under the Power settings screen, it shows: When Idle #] _Sleep___v Though Sleep is grey and unselectable and the building icon "#]" is next to it which on hover says "This setting is enforced by your administrator"
,
Aug 15
Further, from powerd.LATEST in chrome://system/ [0815/113527:INFO:daemon.cc(1307)] Received updated external policy: ac_dim=7m ac_screen_off=7m30s ac_lock=0s ac_idle_warn=0s ac_idle=30m battery_dim=5m battery_screen_off=5m30s battery_lock=0s battery_idle_warn=0s battery_idle=6m30s ac_idle=suspend battery_idle=shutdown lid_closed=shutdown use_audio=1 use_video=1 presentation_factor=2.0 user_activity_factor=2.0 wait_for_initial_user_activity=0 force_nonzero_brightness_for_user_activity=1 (Prefs) [0815/113527:INFO:state_controller.cc(876)] Updated settings: dim=7m screen_off=7m30s lock=0s idle_warn=0s idle=30m (suspend) lid_closed=shutdown use_audio=1 use_video=1 wake_locks= [0815/113528:INFO:daemon.cc(1289)] Chrome is using normal display mode [0815/113529:INFO:audio_client.cc(99)] D-Bus org.chromium.cras ownership changed to :1.20 [0815/113529:INFO:daemon.cc(1366)] Update operation is UPDATE_STATUS_IDLE [0815/113529:INFO:daemon.cc(1366)] Update operation is UPDATE_STATUS_IDLE [0815/113529:INFO:input_watcher.cc(480)] Monitoring input device event9 with sysfs path/sys/devices/pci0000:00/0000:00:1b.0/sound/card1/input9/event9 to identify the wake source [0815/113529:INFO:input_watcher.cc(480)] Monitoring input device event10 with sysfs path/sys/devices/pci0000:00/0000:00:1b.0/sound/card1/input10/event10 to identify the wake source [0815/113529:INFO:suspend_delay_controller.cc(62)] Registering suspend delay 38010883 (btdispatch) of 5000 ms on behalf of :1.38 [0815/113529:INFO:audio_client.cc(162)] Updated audio devices: headphones unplugged, HDMI active [0815/113531:INFO:activity_logger.cc(20)] User activity reported [0815/113535:INFO:daemon.cc(1357)] Session state changed to started [0815/113535:INFO:state_controller.cc(876)] Updated settings: dim=7m screen_off=7m30s lock=0s idle_warn=0s idle=30m (suspend) lid_closed=shutdown use_audio=1 use_video=1 wake_locks= [0815/113537:INFO:daemon.cc(1307)] Received updated external policy: ac_dim=0s ac_screen_off=0s ac_lock=0s ac_idle_warn=0s ac_idle=8h battery_dim=0s battery_screen_off=0s battery_lock=0s battery_idle_warn=0s battery_idle=8h ac_idle=suspend battery_idle=suspend lid_closed=suspend use_audio=1 use_video=1 presentation_factor=2.0 user_activity_factor=2.0 wait_for_initial_user_activity=0 force_nonzero_brightness_for_user_activity=1 (Prefs) [0815/113537:INFO:state_controller.cc(876)] Updated settings: dim=0s screen_off=0s lock=0s idle_warn=0s idle=8h (suspend) lid_closed=suspend use_audio=1 use_video=1 wake_locks= That last bits about the external policy setting ac/battery_idle=8h seems suspect.
,
Aug 20
Confirmed its policy setting w/ my admin, not a chromeos issue. Apologies. My only feedback is it would be nice to make policy settings like this a bit more visible to users, so folks can properly understand where to file an issue. This can probably be closed.
,
Dec 12
Closing per #6. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, May 11 2018