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

Issue 821892 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Not being able to change display layout in display settings

Project Member Reported by afakhry@chromium.org, Mar 14 2018

Issue description

User reported not being able to change the display layout by dragging and dropping the display's squares in the displays settings. Here's what the user reported in  issue 819329 :

================================
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
==========================================


canderson@: Can you please file a feedback report (Alt+Shift+i) right after you attempt to drag and drop displays, and mention this bug in the feedback description?
 
@afakhry, will do very shortly
Status: Assigned (was: Unconfirmed)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment