Incorrect layout applied after first time connect two extending UDL devices
Reported by
adam.kal...@displaylink.com,
Mar 9 2017
|
||||||||||||
Issue descriptionChrome Version: 59.0.3033.0 (Official Build) canary (64bit) Chrome OS Version: Platform 9348.0.0 (Official Build) canary-channel samus Chrome OS Platform: Google_samus.6300.174.0 Network info: not applicable Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1)Switch channel to canary, reboot (2)Attach for the first time two UDL devices with two monitors to USB ports (3)Wait for system to recognize devices and start to extended main laptop screen (4)Open several apps on laptop screen (Settings, Chrome browser as example) (5)Drag one of window with your mouse cursor and move it around the laptop internal screen, observe both UDL screens Expected Result: Application movement should be limited only to laptop internal screen. User should be able to move an application to any UDL extending screen as it is present in Display properties. Actual Result: Both UDL screens are present in Display Properties as extended, however user can't move any application on the extending UDL screen. It looks like that the laptop monitor made a boundary where application can be dragged over. Also when application is moved on the internal laptop screen (when is clicked with a cursor) it is mirrored on other screens. How frequently does this problem reproduce? This problem reproduced for the first time when you attach two external monitors via UDL. What is the impact to the user, and is there a workaround? If so, what is it? Simply user can't move a mouse on the "extending" UDL screens. To workaround this problem you need to change only a bit current layout in display properties. This is healing the system. Video with recorded problem: https://drive.google.com/file/d/0BxMF_wPxgWXtZ1FIR0N0VEdWR2c/view?usp=sharing
,
Mar 9 2017
,
Mar 9 2017
,
Mar 9 2017
From the video, md-settings shows that the 3 displays are not touching. I will try to repro this soon.
,
Mar 9 2017
,
Mar 24 2017
marcheu, is this the bug you told me about?
,
Mar 24 2017
yes this is the same bug we get with two MST monitors.
,
Mar 24 2017
I couldn't repro this issue neither on my setup, nor on marcheu's.
,
Mar 27 2017
,
Mar 28 2017
,
Mar 28 2017
That's a UI bug, so I'm not the right owner. That said it doesn't seem to reproduce any longer so I'm closing it.
,
Mar 30 2017
This problem is still reproducible. I am using Chell CrBook with R59 canary/ R58 dev channel and two UDL devices. This problem is reproducible after power wash (and sometimes after reboot). If you have problems with reproduction try to do a power wash, login user, open any app on internal CrBook screen, then attach the externals UDL screens. Please check todays video at: https://drive.google.com/open?id=0BxMF_wPxgWXtSFNIU2lFSTJCLTQ Thanks, Adam
,
Mar 30 2017
Maybe the layout information wasn't initialized properly on first use. ahmed, can you take a look?
,
Apr 12 2017
,
Apr 14 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d3d4ea43bd26fafa27ae723b7db6ada167034248 commit d3d4ea43bd26fafa27ae723b7db6ada167034248 Author: afakhry <afakhry@chromium.org> Date: Fri Apr 14 02:01:43 2017 Fix expected PlacementList sort order. We sort the displays IDs list by the least significant 8 bits of the IDs. This list is used to fill in the placement list, however, DisplayLayout::Validate() expects the list to be sorted using the full display IDs. This resulted in false positives where we skip applying valid layouts. We also should never persist an invalid layout. BUG= 700020 TEST=manually, +test. Review-Url: https://codereview.chromium.org/2814843007 Cr-Commit-Position: refs/heads/master@{#464654} [modify] https://crrev.com/d3d4ea43bd26fafa27ae723b7db6ada167034248/chrome/browser/chromeos/display/display_preferences.cc [modify] https://crrev.com/d3d4ea43bd26fafa27ae723b7db6ada167034248/ui/display/display.cc [modify] https://crrev.com/d3d4ea43bd26fafa27ae723b7db6ada167034248/ui/display/display.h [modify] https://crrev.com/d3d4ea43bd26fafa27ae723b7db6ada167034248/ui/display/display_layout.cc [modify] https://crrev.com/d3d4ea43bd26fafa27ae723b7db6ada167034248/ui/display/display_layout_builder.cc [modify] https://crrev.com/d3d4ea43bd26fafa27ae723b7db6ada167034248/ui/display/display_layout_unittest.cc [modify] https://crrev.com/d3d4ea43bd26fafa27ae723b7db6ada167034248/ui/display/manager/display_layout_store.cc [modify] https://crrev.com/d3d4ea43bd26fafa27ae723b7db6ada167034248/ui/display/manager/display_manager_utilities.cc [modify] https://crrev.com/d3d4ea43bd26fafa27ae723b7db6ada167034248/ui/display/manager/display_manager_utilities.h
,
Apr 14 2017
,
Jan 22 2018
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by adam.kal...@displaylink.com
, Mar 9 2017