Chrome Version   : 50.0.2661.104 (Official Build) (64-bit)
Chrome OS Version: 7978.76.0 (Official Build) stable-channel auron_yuna
Chrome OS Platform: HP 14 (2014 model), Acer 15 (i5 model)

What steps will reproduce the problem?
(1) connect an external monitor via HDMI. Make an 'extended desktop'
. Everything is as expected
(2) put system to sleep (eg: power_dbus_suspend)
(3) chromebook goes to sleep. Monitor goes to power saving mode. So far, so good.
(4) resume the chromebook

Expected Result:
I want everything to be as before. Extended display, with windows where I left them.

Actual Result:
- chromeos checks the external monitor, which I guess hasn't sufficiently woken up yet
- extended display is turned off, and all windows that were on the external monitor are now on the internal display
- within a second, chromeos now realises that the external monitor is connected, and re-establishes the extended display
- BUT, now all the windows are crammed onto the internal display, and I have to move them back over, manually.

Is this some kind of silly race condition between the displays waking up, and chromeos looking for it?


How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)

It happens on 2 different chromebooks (HP 14, Acer 15) connected to 2 Hanns G 24" screens (with HDMI to DVI), but it doesn't happen when connected to a Hanns G 19" (with HDMI to VGA).

Also, it happens even when chromeos is just turning the screens off (but suspending the os).

What is the impact to the user, and is there a workaround? If so, what is
it?

Impact? Its a complete pain in the rear end to have to manually shift windows over again, periodically. The only workaround is to remember to physically power toggle the monitors immediately before resuming the machine.

Not the best workaround!!!