Issue metadata
Sign in to add a comment
|
Orientation as set in setting is not sticky |
||||||||||||||||||||||||
Issue descriptionChrome Version: 60.0.3112.41 (Official Build) beta (32-bit) OS: CrOS 9592.29.0 (Official Build) beta-channel kevin What steps will reproduce the problem? (1) Ctrl+Shift+Refresh on the login screen to rotate image (2) Do it again, screen should be 180* rotated (3) Login (4) Open Settings (5) Change display orientation to standard (6) Reboot What is the expected result? Login screen is in the correct orientation What happens instead? Login screen is still upside down. Please use labels and text to provide additional information. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Jun 22 2017
How did you change the orientation to standard?
,
Jun 23 2017
It's an option in the dropdown for displays. I think it's the display string for 0.
,
Jun 23 2017
looks like the orientation change made in setting isn't saved. afakhry@, can you take a look?
,
Jun 26 2017
If the device is enrolled against google.com this may be the same issue as crbug.com/735938 and is WAI, corp policy is forcing rotation to 0 degrees which applies on logout / reboot. I've filed internal issue 62898476 to see if corp team can stop forcing orientation for enrolled devices. One quick way to confirm this is indeed the case would be to wipe the device and then *do not* corp enroll it before logging in, that way the device is in consumer mode and does not pickup corp device policy (but will still get user policy). If rotation saves in this config we know it's corp device policy causing the issue. Note you won't be able to get device certs without device being corp-enrolled so you'll need to wipe again.
,
Jun 26 2017
This is probably different issue because rotating using ctrl/shift/+- does get saved.
,
Jun 26 2017
and looks like this is working on 61. Maybe fix isn't merged, or not released yet to 60.
,
Jun 26 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by abodenha@chromium.org
, Jun 22 2017Owner: osh...@chromium.org
Status: Assigned (was: Untriaged)