New issue
Advanced search Search tips

Issue 840867 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 839458
Owner:
Closed: May 2018
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

CrOS update reset preferences

Project Member Reported by edheyl@google.com, May 8 2018

Issue description

Google Chrome	67.0.3396.26 (Official Build) beta (64-bit)
Revision	de708ace5575abaacda89a3ae16cbad2cde45696-refs/branch-heads/3396@{#369}
Platform	10575.22.0 (Official Build) beta-channel eve

What steps will reproduce the problem?
(1) upgraded to 67.0.3396.26
(2) saw the 'critical update' screen
(3) device (eve) reboot once more

What is the expected result?
boot back to upgaded OS, with same preference I had set before the upgrade

What happens instead?
Some preference, screen resolution being the main one I noticed, were reset to default settings, not the resolution/settings I had (for a long time) before the upgrade.

Previous upgrades did not have this issue.

So this appears to be a regression.

 

Comment 1 by wfh@chromium.org, May 18 2018

Labels: -Type-Bug -Pri-3 ReleaseBlock-Stable M-67 Pri-1 Type-Bug-Regression
I got same issue as this in  issue 844498 . what is the best way of getting the team to look at this - could be M-67 regression?

Comment 2 by wfh@chromium.org, May 18 2018

 Issue 844498  has been merged into this issue.

Comment 3 by wfh@chromium.org, May 18 2018

I restarted my chromebook for another update today, update to 67.0.3396.49 (from 67.0.3396.41 - see  issue 844498  for details) and the resolution was reset again.
Owner: malaykeshav@chromium.org
malaykeshav@ please dedupe appropriately.

Labels: -ReleaseBlock-Stable
Mergedinto: 839458
Status: Duplicate (was: Untriaged)
The first resolution change was intentional due to the launch of a new feature that handles display scaling differently.

However we received a ton of feedback due to this sudden pref change after the update. This led us to rethink the way we launch the feature. We plan to launch it again for the next milestone (M68) in such a way that users do not notice a preference change. 

In the meantime we also do not want the stable users of M67 to face the same bad UX as our beta/dev users did, so we had to disable it on M67. This disabling is what was noticed in #3.

Sign in to add a comment