Monitor orientation is lost following reboot |
|||||||||||||
Issue descriptionChrome Version: 59.0.3071.25 (Official Build) dev (64-bit) OS: ChromeOS Panther What steps will reproduce the problem? (1) Connect two monitors to the device. (2) Rotate the secondary monitor and configure it to 270-degree rotation. (3) Reboot the device. (4) Sign-in again. What is the expected result? Expect that the system starts up with the secondary monitor configured with 270-degree rotation. What happens instead? System starts up with secondary monitor in normal rotation. Even after signing in, it stays at normal rotation.
,
Apr 27 2017
sounds like a regression. ahmed@ can you look into this?
,
May 9 2017
,
May 17 2017
CB Plus here, auto rotation broken. Haven't used ext monitor since update to 59 I don't believe. https://www.reddit.com/r/chromeos/comments/6atl6d/chromebook_plus_owners_dont_upgrade_to_beta_59/
,
May 17 2017
Re #4: Doug, that sounds likely to be a different issue - I'd suggest filing a new bug for it and perhaps mentioning this bug number in the description, in case the two turn out to be related.
,
May 17 2017
Thanks W, done. https://bugs.chromium.org/p/chromium/issues/detail?id=723697
,
May 24 2017
,
Jun 2 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/100ef2b48dbab733c8cebe556a673f4f16d20c49 commit 100ef2b48dbab733c8cebe556a673f4f16d20c49 Author: malaykeshav <malaykeshav@chromium.org> Date: Fri Jun 02 18:43:26 2017 Sets the rotation source as USER when using the system display API The rotation preference is not persistent across reboot since we only store the preference if the rotation source is 'USER'. With the move to MD settings, we now use the System Display API to update any display settings, which still uses the source of rotation as ACTIVE. This change updates the source of rotation to USER. We persist the setting even if the change has been made by an application. (This is consistent with the other settings that are being set via this API.) BUG= 716110 COMPONENT=Display Info Provider, Chrome Settings Review-Url: https://codereview.chromium.org/2920703003 Cr-Commit-Position: refs/heads/master@{#476734} [modify] https://crrev.com/100ef2b48dbab733c8cebe556a673f4f16d20c49/chrome/browser/extensions/display_info_provider_chromeos.cc
,
Jun 2 2017
,
Jun 26 2017
,
Jun 26 2017
can you merge this to 60?
,
Jun 26 2017
,
Jun 26 2017
This bug requires manual review: M60 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 26 2017
,
Jun 27 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c6d6bd1be3e6042c5022afdb40fc5334ed0bc7e0 commit c6d6bd1be3e6042c5022afdb40fc5334ed0bc7e0 Author: F#m <malaykeshav@chromium.org> Date: Tue Jun 27 01:26:18 2017 Sets the rotation source as USER when using the system display API The rotation preference is not persistent across reboot since we only store the preference if the rotation source is 'USER'. With the move to MD settings, we now use the System Display API to update any display settings, which still uses the source of rotation as ACTIVE. This change updates the source of rotation to USER. We persist the setting even if the change has been made by an application. (This is consistent with the other settings that are being set via this API.) BUG= 716110 COMPONENT=Display Info Provider, Chrome Settings Review-Url: https://codereview.chromium.org/2920703003 Cr-Original-Commit-Position: refs/heads/master@{#476734} Review-Url: https://codereview.chromium.org/2954343003 . Cr-Commit-Position: refs/branch-heads/3112@{#474} Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897} [modify] https://crrev.com/c6d6bd1be3e6042c5022afdb40fc5334ed0bc7e0/chrome/browser/extensions/display_info_provider_chromeos.cc
,
Jul 10 2017
,
Jul 27 2017
,
Jul 27 2017
Verified in Chrome OS 9592.71.0, 60.0.3112.80. |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by w...@chromium.org
, Apr 27 2017