This is relatively widespread on Chromeboxes, so it'd be ideal if we can get the fix in current milestone.

+igo@, could you share more details? Does the issue of ChromeBoxes only occur after update from M63 to later version? We have a memory corruption bug fix in M64 which may cause the similar issue. See https://bugs.chromium.org/p/chromium/issues/detail?id=800471#c8 for details.

Here's another report. Both are on M65 Beta, and updates within M65.

I believe all reports are (1) HDMI display and (1) USB-C display

User feedback report:
https://listnr.corp.google.com/report/85118805401

URL: chrome://settings/help
Product Version: 65.0.3325.89 beta
UI Language: en-US

Description:
After rebooting for an update, ChromeOS lost which order my monitors are in.

+dcastagna@
Do you know if there is any change in M65 that makes the order of connectors retrieved from drmModeGetResources(fd) [1] change? If the order of connectors change, the display id may change as well. And the Chrome OS does not recognize the display and, thus, will use default display layout which changes the display original positions.

[1] https://cs.chromium.org/chromium/src/ui/ozone/platform/drm/common/drm_util.cc?q=GetAvailableDisplayControllerInfos&sq=package:chromium&l=255

+jeffbailey@google.com
Do you remember the version of Chrome before you update and find the bug in https://listnr.corp.google.com/report/85118805401 ?

No, sorry, this was a fresh device so it was just whatever it booted with.
:-/

Wasn't there a change in M65 to the way we construct display identifiers
for each monitor?

Re #7: Yes, there was a fix that landed in M-65 and merged back to M-64 (See  issue 717371 , and my comment here: https://bugs.chromium.org/p/chromium/issues/detail?id=800471#c8).

This fix might affect you only if you are upgrading for M63- to M64+, but not from M64 to M65 and so on.

I have an issue that seems related. After updating to the last stable build, some Acer Chromebooks we have rebooted with moved-around displays. The each use 2 external monitors, one is an HDMI out on the computer and the other is from a USB-C dock/bridge with a HDMI out. After restarting, the users attempted to rearrange the displays and the result was that each display's UI (a rectangle with the name of the display) would appear to freeze and not respond to drag-and-drops. The end result is that the "positions" of the screens are now super wonky and the user has to move their mouse to far corners to move to other monitors.

Google Support had me try to switch to the Beta channel to see if 65 fixed it. It did not.

Any thoughts?

Hardware and OS
Model
Chromebook 14 for work (CP5-471)
Serial Number
NXGE8AA004706190A97600
MEID
WiFi MAC Address
c821580ff997
Ethernet MAC Address
0023561c0004
Google Chrome Version
64.0.3282.167
Platform Version
10176.72.0 (Official Build) stable-channel lars
Firmware Version
TPM Firmware Version
628
Boot Mode
Verified
Enrollment Date
Sep 22, 2017
Directory API ID
ed738773-cff5-4620-a7d5-b949e0a2f41c

Re#9: This sounds like a different issue, I filed bug 821892 to track it. Please file a feedback report as instructed there on that new bug. Thanks!

Close this since it is not repro for newer versions.