New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 611715 link

Starred by 1 user
Status: WontFix
Owner:
█ dskaram@chromium.org
Last visit > 30 days ago
Closed: May 2016
Cc:
█ medland@google.com
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

FR: Prevent Chromebook from sleeping when connected to an external monitor and the lid is closed

Project Member Reported by medland@google.com, May 13 2016 
UserAgent: Mozilla/5.0 (X11; CrOS x86_64 8172.28.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.42 Safari/537.36
Platform: 8172.28.0 (Official Build) beta-channel samus

Steps to reproduce the problem:
Currently if a Chromebook is connected to an external monitor and close the lid of the Chromebook the device goes to sleep. 
The use case is for users who wish to use their Chromebook with an external keyboard, mouse and monitor and use the device in a 'docked' mode with the lid closed.

What is the expected behavior?
User has external monitor connected and closes the lid of the Chromebook. The Chromebook maintains state and stays awake until the monitor is disconnected or screen timeout occurs.

What went wrong?
Chromebook goes to sleep when lid is closed.

Did this work before? No 

Chrome version: 51.0.2704.42  Channel: beta
OS Version: 8172.28.0
Flash Version: Shockwave Flash 22.0 r0

Comment 1 by dskaram@chromium.org, May 13 2016

Cc: medland@google.com
Owner: dskaram@chromium.org
Status: Assigned (was: Unconfirmed)
Did we reproduce this locally ourselves by the way?

Interestingly there is a Issue 488091 where they want the exact opposite i.e. to lock screen even if we are casting to an external display. The comments from that bug seem to imply that the requested behavior here already exists on Chrome OS:

"Right now having my external monitor plugged in means my chromebook never locks is pretty bad."


Can you please verify on your side?

Comment 2 by medland@google.com, May 13 2016 

Okay tested this and it works fine. I believe this is related to using a DisplayLink device with monitors.

I suggest we close this bug and I'll reopen once I've tested with a DisplayLink+monitor

Comment 3 by dskaram@chromium.org, May 13 2016

Status: WontFix (was: Assigned)
OK closed this. Let's drill to the bottom of this. Happy to help if we do find a bug that needs to be fixed.
►

Sign in to add a comment