Notes
** This might be related to  Issue 605554 .

** This *does not* happen when the Chromebook is connected to an external display directly i.e. this only surfaces with DisplayLink.

** Related Issue 488091. There we don't sleep if we are casting to an external display. Users expect similar behavior (contrary to what the bug says i.e. we established that this is not really a bug) and we should be consistent with that behavior.

It shouldn't go to sleep, whether that's an internal or an external display, this what docked mode is supposed to do. Are you saying that the laptop goes to sleep when an external display is connected and you close the lid? That would be the bug.

Yes it is going to sleep per customer feedback so it's definitely being considered a bug. What I meant by relating to Issue 488091 is a similar discussion on whether the device should go to sleep and the conclusion was it shouldn't.

Our deployment folks said they could reproduce on their side. Is this something you also see (I don't have access to any DisplayLink hardware).

Adding more people and ozone folks, since this is going to be a problem on the Chrome side.

I vaguely remember that dock mode was working with UDL at some point in the past. The decision to go to sleep is made by chrome.

Is this happening on the latest canary? Which board is it.

This was definitely working before. Is it possible to get a feedback report? (I'm interested in the logs to see what the display state is from Chrome's perspective).

Trying to get some more info from the customer.

#CBC-RS/TC-watchlist

Confirmed by customer that the issue pertains to the Chromebook going to sleep after being idle. Chromebook can only be woken up by opening the lid. 

So to confirm - Chromebook with lid closed connected to a DisplayLink works as intended however, if the Chromebook is left idle and goes to sleep it is not possible to bring out of sleep by moving the mouse or touching the keyboard. 

Thanks Luke. Can Chrome be woken up with mouse and keyboard when connected directly to an external monitor? I'm just wondering whether this has any relationship to DisplayLink.

+oshima - this is regarding docked mode. When lid is closed and external display is attached:

(1) is the device allowed to go to sleep after a period of idle?
(2) is the device expected to be woken up with mouse and keyboard after (1)?

+derat@, can you answer the questions above?

I wonder if this has something to do with lucid sleep. +dbasehore@

> When lid is closed and external display is attached:
> (1) is the device allowed to go to sleep after a period of idle?

Yes.

(2) is the device expected to be woken up with mouse and keyboard after (1)?

It depends on how the particular device handles USB.

It's unlikely that DisplayLink or lucid sleep have anything to do with this. Which device is being discussed here?

re:#13 (2) this may be complicated by the fact that DisplayLink devices use USB.

Consider a "normal" external display (e.g. HDMI), when the device is put in docked mode and is woken up by mouse and keyboard, how long does Chrome have to decide that the external display is still attached, and therefore the device should wake up despite that the lid is closed?

It would be really great if we could get a feedback report (Alt-Shift-i) taken right after the issue occurs so we're not just speculating here. :-P

The terminology is dated, but Chrome reports whether it's "projecting" a.k.a. "presenting" or not to powerd over D-Bus (see chromeos::PowerManagerClient::SetIsProjecting()). We are presenting when there are multiple displays connected and one of them is internal.

In powerd, the lid-closed action is overridden while Chrome reports that the system is presenting. This is how docked mode is implemented.

If the system is waking in response to USB input but then Chrome reports that the system is no longer presenting due to the DisplayLink adapter still being powered off or something, then it's possible that powerd would resuspend the system immediately. There's no timeout for this on the powerd side, though.

But again, I'm just guessing. We need logs.

I'll ask the customer to provide logs

We now have a reproducible scenario from the customer along with logs. Seems the Chromebook is waking up when docked, but the screen is not projecting. Attaching description here:


"Today I am working with the pixel CB and I the issue while in docked mode using a DL 3.0.
 
The CB did not wake up from sleep when moving the mouse. At least it did not wake up the external monitor. I also tried to hit some keys on the keyboard, did not wake the monitor either. I had to open and close the lid again. Interesting was, that my keyboard input got through and password field to unlock the session had captured my input. It seems the CB itself did wake up, but not the external monitor. I’ve captured the logs:
 
Alt shift i logs from around 14:25 +- 15 min today. I missed to note the exact time stamp."
 

Is https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=docked&lReport=11132531039 the feedback report? Just guessing since I don't see the customer's email address here.

If that's correct, I don't think that it's a powerd issue. Note that the system didn't suspend; the screen was just turned off due to inactivity. At 14:06:10, user activity was observed and powerd asked Chrome to turn the display back on.

----

[0706/135211:INFO:daemon.cc(533)] Lid closed
[0706/135211:INFO:wakeup_controller.cc(166)] Un-inhibiting /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:04F2:1338.0001/input/input6
[0706/135211:INFO:wakeup_controller.cc(166)] Un-inhibiting /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:04F2:1338.0002/input/input7
[0706/135211:INFO:wakeup_controller.cc(166)] Un-inhibiting /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2/0003:04F2:1338.0003/input/input8
[0706/135211:INFO:wakeup_controller.cc(166)] Inhibiting /sys/devices/pci0000:00/INT3432:00/i2c-0/i2c-ATML0000:01/input/input4
[0706/135211:INFO:wakeup_controller.cc(166)] Inhibiting /sys/devices/pci0000:00/INT3433:00/i2c-1/i2c-ATML0001:01/input/input5
[0706/135211:INFO:wakeup_controller.cc(166)] Inhibiting /sys/devices/platform/i8042/serio0/input/input3
[0706/135211:INFO:wakeup_controller.cc(153)] Enabling wakeup for /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:04F2:1338.0001/input/input6 through /sys/devices/pci0000:00/0000:00:1
4.0/usb1/1-1
[0706/135211:INFO:wakeup_controller.cc(153)] Enabling wakeup for /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:04F2:1338.0002/input/input7 through /sys/devices/pci0000:00/0000:00:1
4.0/usb1/1-1
[0706/135211:INFO:wakeup_controller.cc(153)] Enabling wakeup for /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2/0003:04F2:1338.0003/input/input8 through /sys/devices/pci0000:00/0000:00:1
4.0/usb1/1-1
[0706/135211:INFO:wakeup_controller.cc(153)] Disabling wakeup for /sys/devices/pci0000:00/INT3432:00/i2c-0/i2c-ATML0000:01/input/input4 through /sys/devices/pci0000:00/INT3432:00/i2c-0/i2c-ATML
0000:01
[0706/135211:INFO:wakeup_controller.cc(153)] Disabling wakeup for /sys/devices/platform/i8042/serio0/input/input3 through /sys/devices/platform/i8042/serio0
[0706/135211:INFO:state_controller.cc(846)] Turning panel off after entering docked mode
[0706/135211:INFO:display_power_setter.cc(72)] Asking Chrome to turn internal display off and external displays on
[0706/135211:INFO:internal_backlight_controller.cc(676)] Setting brightness to 0 (0%) over 0 ms
[0706/135211:INFO:state_controller.cc(889)] Ready to perform lid-closed action (no-op)
[0706/135211:INFO:daemon.cc(1405)] Chrome is using presentation display mode
...
[0706/135752:INFO:state_controller.cc(89)] Dimming screen after 1m
[0706/135802:INFO:state_controller.cc(89)] Turning screen off after 1m10s
[0706/135802:INFO:display_power_setter.cc(72)] Asking Chrome to turn all displays off
[0706/135802:INFO:daemon.cc(1405)] Chrome is using presentation display mode
...
[0706/140610:INFO:daemon.cc(1385)] Saw user activity
[0706/140610:INFO:state_controller.cc(96)] Undimming screen
[0706/140610:INFO:state_controller.cc(96)] Turning screen on
[0706/140610:INFO:display_power_setter.cc(72)] Asking Chrome to turn internal display off and external displays on
[0706/140610:INFO:daemon.cc(1405)] Chrome is using presentation display mode
...
[0706/140625:INFO:daemon.cc(542)] Lid opened
[0706/140625:INFO:state_controller.cc(846)] Turning panel on after leaving docked mode
[0706/140625:INFO:display_power_setter.cc(72)] Asking Chrome to turn all displays on
[0706/140626:INFO:internal_backlight_controller.cc(676)] Setting brightness to 348 (60.5%) over 0 ms
[0706/140626:INFO:keyboard_backlight_controller.cc(471)] Setting brightness to 40 (40%) over 200 ms
[0706/140626:INFO:wakeup_controller.cc(166)] Un-inhibiting /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:04F2:1338.0001/input/input6
[0706/140626:INFO:wakeup_controller.cc(166)] Un-inhibiting /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:04F2:1338.0002/input/input7
[0706/140626:INFO:wakeup_controller.cc(166)] Un-inhibiting /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2/0003:04F2:1338.0003/input/input8
[0706/140626:INFO:wakeup_controller.cc(166)] Un-inhibiting /sys/devices/pci0000:00/INT3432:00/i2c-0/i2c-ATML0000:01/input/input4
[0706/140626:INFO:wakeup_controller.cc(166)] Un-inhibiting /sys/devices/pci0000:00/INT3433:00/i2c-1/i2c-ATML0001:01/input/input5
[0706/140626:INFO:wakeup_controller.cc(166)] Un-inhibiting /sys/devices/platform/i8042/serio0/input/input3
[0706/140626:INFO:wakeup_controller.cc(153)] Enabling wakeup for /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:04F2:1338.0001/input/input6 through /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1
[0706/140626:INFO:wakeup_controller.cc(153)] Enabling wakeup for /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:04F2:1338.0002/input/input7 through /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1
[0706/140626:INFO:wakeup_controller.cc(153)] Enabling wakeup for /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2/0003:04F2:1338.0003/input/input8 through /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1
[0706/140626:INFO:wakeup_controller.cc(153)] Enabling wakeup for /sys/devices/pci0000:00/INT3432:00/i2c-0/i2c-ATML0000:01/input/input4 through /sys/devices/pci0000:00/INT3432:00/i2c-0/i2c-ATML0000:01
[0706/140626:INFO:wakeup_controller.cc(153)] Enabling wakeup for /sys/devices/platform/i8042/serio0/input/input3 through /sys/devices/platform/i8042/serio0
[0706/140626:INFO:daemon.cc(1405)] Chrome is using presentation display mode
[0706/140626:INFO:daemon.cc(533)] Lid closed
[0706/140626:INFO:wakeup_controller.cc(166)] Un-inhibiting /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:04F2:1338.0001/input/input6
[0706/140626:INFO:wakeup_controller.cc(166)] Un-inhibiting /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:04F2:1338.0002/input/input7
[0706/140626:INFO:wakeup_controller.cc(166)] Un-inhibiting /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2/0003:04F2:1338.0003/input/input8
[0706/140626:INFO:wakeup_controller.cc(166)] Inhibiting /sys/devices/pci0000:00/INT3432:00/i2c-0/i2c-ATML0000:01/input/input4
[0706/140626:INFO:wakeup_controller.cc(166)] Inhibiting /sys/devices/pci0000:00/INT3433:00/i2c-1/i2c-ATML0001:01/input/input5
[0706/140626:INFO:wakeup_controller.cc(166)] Inhibiting /sys/devices/platform/i8042/serio0/input/input3
[0706/140626:INFO:wakeup_controller.cc(153)] Enabling wakeup for /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:04F2:1338.0001/input/input6 through /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1
[0706/140626:INFO:wakeup_controller.cc(153)] Enabling wakeup for /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:04F2:1338.0002/input/input7 through /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1
[0706/140626:INFO:wakeup_controller.cc(153)] Enabling wakeup for /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2/0003:04F2:1338.0003/input/input8 through /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1
[0706/140626:INFO:wakeup_controller.cc(153)] Disabling wakeup for /sys/devices/pci0000:00/INT3432:00/i2c-0/i2c-ATML0000:01/input/input4 through /sys/devices/pci0000:00/INT3432:00/i2c-0/i2c-ATML0000:01
[0706/140626:INFO:wakeup_controller.cc(153)] Disabling wakeup for /sys/devices/platform/i8042/serio0/input/input3 through /sys/devices/platform/i8042/serio0
[0706/140626:INFO:state_controller.cc(846)] Turning panel off after entering docked mode
[0706/140626:INFO:display_power_setter.cc(72)] Asking Chrome to turn internal display off and external displays on
[0706/140627:INFO:internal_backlight_controller.cc(676)] Setting brightness to 0 (0%) over 0 ms
[0706/140627:INFO:keyboard_backlight_controller.cc(471)] Setting brightness to 0 (0%) over 2000 ms
[0706/140627:INFO:keyboard_backlight_controller.cc(471)] Setting brightness to 0 (0%) over 0 ms
[0706/140627:INFO:state_controller.cc(889)] Ready to perform lid-closed action (no-op)
[0706/140627:INFO:daemon.cc(1405)] Chrome is using presentation display mode

Here are the corresponding Chrome logs. I don't think I see anything strange there either.

[1359:1359:0706/140610:VERBOSE1:display_configurator.cc(853)] SetDisplayPower: power_state=INTERNAL_OFF_EXTERNAL_ON flags=0, configure timer=Stopped
[1359:1359:0706/140610:VERBOSE1:update_display_configuration_task.cc(64)] OnDisplaysUpdated: new_display_state=SINGLE new_power_state=INTERNAL_OFF_EXTERNAL_ON flags=0 force_configure=0 display_count=2
[1359:1359:0706/140610:VERBOSE1:display_configurator.cc(223)] EnterState: display=SINGLE power=INTERNAL_OFF_EXTERNAL_ON
[1359:1359:0706/140610:VERBOSE1:display_configurator.cc(1013)] OnConfigured: success=1 new_display_state=SINGLE new_power_state=INTERNAL_OFF_EXTERNAL_ON
[1359:1359:0706/140610:VERBOSE1:display_manager.cc(548)] OnNativeDisplaysChanged(1):DisplayInfo[7515455687266064] native bounds=0,0 1920x1200, size=1920x1200, scale=1.000000, overscan=0,0,0,0, rotation=0, ui-scale=1.000000, touchscreen=unknown, input_devices=[]
[1359:1359:0706/140610:VERBOSE1:display_color_manager_chromeos.cc(213)] No ICC file found with product id: 30e42e04 for display id: 13761487533244416
[1359:1359:0706/140610:VERBOSE1:display_color_manager_chromeos.cc(213)] No ICC file found with product id: 1ab35308 for display id: 7515455687266064
...
[1359:1359:0706/140625:VERBOSE1:display_configurator.cc(853)] SetDisplayPower: power_state=ALL_ON flags=0, configure timer=Stopped
[1359:1359:0706/140625:VERBOSE1:update_display_configuration_task.cc(64)] OnDisplaysUpdated: new_display_state=DUAL_EXTENDED new_power_state=ALL_ON flags=0 force_configure=0 display_count=2
[1359:1359:0706/140625:VERBOSE1:display_configurator.cc(223)] EnterState: display=DUAL_EXTENDED power=ALL_ON
[1359:1359:0706/140626:VERBOSE1:display_configurator.cc(1013)] OnConfigured: success=1 new_display_state=DUAL_EXTENDED new_power_state=ALL_ON
[1359:1359:0706/140626:VERBOSE1:display_manager.cc(550)] OnNativeDisplaysChanged(2) [0]=DisplayInfo[13761487533244416] native bounds=0,0 2560x1700, size=2560x1700, scale=2.000000, overscan=0,0,0,0, rotation=0, ui-scale=1.000000, touchscreen=yes, input_devices=[8], [1]=DisplayInfo[7515455687266064] native bounds=0,1760 1920x1200, size=1920x1200, scale=1.000000, overscan=0,0,0,0, rotation=0, ui-scale=1.000000, touchscreen=unknown, input_devices=[]
[1359:1359:0706/140626:VERBOSE1:display_color_manager_chromeos.cc(213)] No ICC file found with product id: 1ab35308 for display id: 7515455687266064
[1359:1359:0706/140626:VERBOSE1:display_color_manager_chromeos.cc(213)] No ICC file found with product id: 30e42e04 for display id: 13761487533244416
[1359:1359:0706/140626:VERBOSE1:display_configurator.cc(853)] SetDisplayPower: power_state=INTERNAL_OFF_EXTERNAL_ON flags=0, configure timer=Stopped
[1359:1359:0706/140626:VERBOSE1:update_display_configuration_task.cc(64)] OnDisplaysUpdated: new_display_state=SINGLE new_power_state=INTERNAL_OFF_EXTERNAL_ON flags=0 force_configure=0 display_count=2
[1359:1359:0706/140626:VERBOSE1:display_configurator.cc(223)] EnterState: display=SINGLE power=INTERNAL_OFF_EXTERNAL_ON
[1359:1359:0706/140627:VERBOSE1:display_configurator.cc(1013)] OnConfigured: success=1 new_display_state=SINGLE new_power_state=INTERNAL_OFF_EXTERNAL_ON
[1359:1359:0706/140627:VERBOSE1:display_manager.cc(548)] OnNativeDisplaysChanged(1):DisplayInfo[7515455687266064] native bounds=0,0 1920x1200, size=1920x1200, scale=1.000000, overscan=0,0,0,0, rotation=0, ui-scale=1.000000, touchscreen=unknown, input_devices=[]
[1359:1359:0706/140627:VERBOSE1:display_color_manager_chromeos.cc(213)] No ICC file found with product id: 30e42e04 for display id: 13761487533244416
[1359:1359:0706/140627:VERBOSE1:display_color_manager_chromeos.cc(213)] No ICC file found with product id: 1ab35308 for display id: 7515455687266064

Displaylink support (whether that's through udl or evdi, or even both) is basically using a different drm driver than the built-in one (i915, rockchip, etc.). So my first question is: are we sure that Chrome is turning on the displays on the right drivers? Maybe it doesn't iterate all of them somehow? It's hard to say from the log.

From the chrome_system_log in the above mentioned feedback report the last operation is a modeset operation for the evdi device.

[3139:3305:0706/140610:VERBOSE1:drm_display.cc(102)] DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=20 connector=29 origin=0,0 size=0x0
[3139:3305:0706/140610:VERBOSE1:drm_display.cc(102)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,0 size=1920x1200
[1:1:0706/140621:ERROR:PlatformKeyboardEvent.cpp(84)] Not implemented reached in static bool blink<IPv6: 2>PlatformKeyboardEvent<IPv6: 6>urrentCapsLockState()
[3139:3305:0706/140625:WARNING:screen_manager.cc(99)] Display controller (crtc=20) already present.
[3139:3305:0706/140625:WARNING:screen_manager.cc(99)] Display controller (crtc=21) already present.
[3139:3305:0706/140625:VERBOSE1:drm_display.cc(102)] DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=20 connector=29 origin=0,0 size=2560x1700
[3139:3305:0706/140626:VERBOSE1:drm_display.cc(102)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,1760 size=1920x1200
[1:1:0706/140626:ERROR:PlatformKeyboardEvent.cpp(84)] Not implemented reached in static bool blink<IPv6: 2>PlatformKeyboardEvent<IPv6: 6>urrentCapsLockState()
[1:1:0706/140626:ERROR:PlatformKeyboardEvent.cpp(84)] Not implemented reached in static bool blink<IPv6: 2>PlatformKeyboardEvent<IPv6: 6>urrentCapsLockState()
[1:1:0706/140626:WARNING:ipc_message_attachment_set.cc(57)] MessageAttachmentSet destroyed with unconsumed descriptors: 0/1
[3139:3305:0706/140626:WARNING:screen_manager.cc(99)] Display controller (crtc=20) already present.
[3139:3305:0706/140626:WARNING:screen_manager.cc(99)] Display controller (crtc=21) already present.
[3139:3305:0706/140626:VERBOSE1:drm_display.cc(102)] DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=20 connector=29 origin=0,0 size=0x0
[3139:3305:0706/140627:VERBOSE1:drm_display.cc(102)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,0 size=1920x1200

Sorry, I should further clarify:

1) the state previous to the first log line is all displays are turned off:

[3139:3305:0706/135802:VERBOSE1:drm_display.cc(102)] DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=20 connector=29 origin=0,0 size=0x0
[3139:3305:0706/135802:VERBOSE1:drm_display.cc(102)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,0 size=0x0

2) At 14:06:10 the external (UDL) display is being turned on. (Presumably this is where the user doesn't notice anything.
3) At 14:06:25 the lid is opened and both internal and external displays are turned on again (in extended mode).
4) At 14:06:26 the lid is closed and the external display is the only active one.

These seem to match the timings in powerd and the other chrome log.

Hmm it would be interesting to look at the output of modetest while the problem is happening then. It would tell us if the driver has a bug.

Another way to know if evdi has a bug is to try the same thing with udl.

Any scenario we can have the cusotmer go through to produce more useful logs?

If no one in MTV has a DisplayLink 3.0 adapter handy, I can order one to try to get output from a dev-mode samus.

Just for completeness, looks like it's a Fujitsu USB 3.0 Port Replicator (PR08):

[46332.919850] usb 2-2.1: New USB device found, idVendor=17e9, idProduct=430c
[46332.919879] usb 2-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[46332.919901] usb 2-2.1: Product: PR08 DisplayPort Dock
[46332.919918] usb 2-2.1: Manufacturer: DisplayLink
[46332.919934] usb 2-2.1: SerialNumber: 10037375

It'd probably be interesting to know if it happens with other DL adapters.

I've got a v2 and v3 (not the same brand) device. I'll try and see if I can reproduce the issue in the meantime.

For reference, the user is on R51-8172.60.0 and I was able to re-produce the issue. (using a v2 device)

I've also tested on R52-8350.46.0 with a v2 and a v3 device and the issue does not reproduce anymore.

The only Chrome change in between, which is related to UDL, is https://codereview.chromium.org/1780013002 (so possibly related). (Not confirmed)

Additional notes: I've traced the modeset calls in Chrome and we weren't missing any. From Chrome's perspective the display was up and I've even seen 3 page flips after. Though the modetest output did validate that the UDL device did not have a mode configured. If it is related to the above change we're likely also encountering crbug.com/454819 (or at least a variation of that).


For reference this is the v3 device I've used (has a DL-3500 chipset):

[  368.873102] usb 2-2: new SuperSpeed USB device number 3 using xhci_hcd
[  368.884387] usb 2-2: New USB device found, idVendor=17e9, idProduct=4301
[  368.884410] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  368.884428] usb 2-2: Product: Plugable USB3-HDMI-DVI
[  368.884441] usb 2-2: Manufacturer: DisplayLink
[  368.884454] usb 2-2: SerialNumber: PLUG412130814041990188

Yes that does sound like the same issue... Can we get affected people to test on the beta/dev (whichever is 52) channel?

Sorry my last post had 2 errors. Correct is:

Hi all, i've tested it on M52 BETA. If i just use the chromebook (CB) without citrix session it works as expected.

Setup:
HP 11" G4
external display via HDMI (lid open)
timeout sleep in admin console = 15 min

Whenever i do not touch the CB it goes into sleep and locks the session as expected. I've tested it several times.

Then:
1. I've started the citrix session and worked with my virtual client a couple of minutes.
2. Do nothing and wait for timeout

REsult:
CB does not go into sleep
After 15 minutes the CB session locks, but remains awake (no sleep)
Even after 30 min the CB did not go into sleep

After logging in again i've sent the Alt shift i logs (2:30 CET) user thorsten.bergmann@siemens.com

Will now log out, reboot and test again. 

#32: This bug is about the display not turning back on when using a DisplayLink adapter. It sounds like you're discussing something separate in #32 (the system not going to sleep while you have an active Citrix session). I've copied your comment to new  issue 630752 .

This seems to be working fine now on 55.

Google Chrome	55.0.2883.29 (Official Build) beta (64-bit)
Platform	8872.27.0 (Official Build) beta-channel samus

Please reopen if this is not the case.