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

Issue 604535 link

Starred by 3 users
Status: Fixed
Owner:
█ warx@chromium.org
Last visit > 30 days ago
Closed: Jun 2018
Cc:
abodenha@chromium.org
█ kuscher@chromium.org
█ marc...@chromium.org
osh...@chromium.org
dbasehore@chromium.org
jdufault@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Window locations are lost when resuming from sleep (on Pixel 2 plugged into 2 monitors)

Project Member Reported by kanliu@chromium.org, Apr 18 2016 
Version: 51.0.2704.0 dev (64-bit)
OS: Chrome

What steps will reproduce the problem?
(1) Plug a Pixel 2 into two monitors (using the two usb-c ports)
(2) Place windows across the 2 different monitors 
(3) Close lid and let device go to sleep for a while
(4) Return to the device later (this happens every morning to me)
(5) Wake and unlock device

What is the expected output?
Windows are restored to where they were on the two different monitors before it went to sleep.

What do you see instead?
Windows are all put back into the 1st monitor and resized to the size of the laptop screen.

Here's the link to my feedback report: http://feedback/#/Report/8087644871

Comment 1 by abodenha@chromium.org, Apr 18 2016

Labels: M-52
Owner: jdufault@chromium.org
Status: Assigned (was: Untriaged)
Clarifying the failure case a bit:
Device is in docked mode with 2 external displays.
Lock the device.
Leave it overnight.

The next morning unlock the device and notice that all windows are moved to a single display.

This config didn't work at all until recently so this is likely just an unhandled edge case in the new support.

Comment 2 by osh...@chromium.org, Apr 19 2016

Cc: dbasehore@chromium.org
This could be due to lucid sleep, which may detect 3 displays and applies different layout information.

+dbasehore@, who is working on improving the display handling during lucid sleep.
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 13 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by jdufault@chromium.org, Mar 22 2017

Cc: jdufault@chromium.org
Owner: warx@chromium.org

Comment 6 by osh...@chromium.org, Mar 22 2017

Cc: marc...@chromium.org
+marcheu@

This may actually be WAI. One possibility is that monitors went off or went power saving state (whose behavior can vary between displays), which disconnected displays.

Comment 7 by weifangsun@chromium.org, Mar 9 2018

Components: UI>Shell>MultipleMonitor

Comment 8 by warx@chromium.org, Jun 20 2018

Status: Fixed (was: Assigned)
This shall be fixed by 740268
►

Sign in to add a comment