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

Issue 724421 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Unable to modify settings in 'Manage other users' page on every first login as owner.

Project Member Reported by jbanavatu@chromium.org, May 19 2017

Issue description

Chrome Version:60.0.3102.0/9565.0.0 dev channel Kip,Paine,Blaze
OS: Chrome OS

What steps will reproduce the problem?
(1)Recover build via USB >> Sign in to chrome as Owner 
(2)Go to chrome://md-settings/accounts page and Observe 

Expected: For owner, all options in manage other users should be editable.
Actual: Instead,unable to modify the settings(All options are seen disable with tool-tip as 'This settings are managed by owner' even on logging in as owner) (Please refer video)

Note: This issue is seen only when logged in for the first time as owner.Once we sign out and sign-in everything looks fine.

This is regression issue as no such behavior is seen in 59.0.3071.57/9460.43.0 beta channel Kip.

Attaching screen-cast for reference.
 
Actual.mp4
10.8 MB View Download
Cc: xiy...@chromium.org
Did you try reloading the settings page?

xiyuan@ - is it possible that the mechanism we use to determine whether the user is the owner (ProfileHelper::IsOwnerProfile(GetProfile());) might be incorrect when we first load the settings page?

Comment 2 by xiy...@chromium.org, May 19 2017

Not really a regression.

ProfileHelper::IsOwnerProfile() is fine. But owner status is static. It is only static after owner key is verified on chrome start. The first time signing in when user takes ownership, we also need an extra 1+ seconds to generate the key so it would take a bit longer. After owner key is verified, ProfileHelper::IsOwnerProfile() might change its return failure.

Another possible repro is to open settings page, then kill chrome to force it restart. And owner section probably would be disabled on restart too.

The reliable way to determine owner status is using OwnerSettingsService::IsOwnerAsync. The callback will be called when owner status is determined. Is it possible to do that?

Comment 3 by xiy...@chromium.org, May 19 2017

Correction to #2: I mean owner status is NOT static. :p
Yep, the extension API is already async, I will make that change, thanks!

Comment 5 by dbeam@chromium.org, May 22 2017

Labels: Hotlist-MD-Settings-PeopleCrOS
Cc: zalcorn@chromium.org
Labels: -M-60 M-61
Status: Fixed (was: Assigned)
This is enough of an edge case that I don't think we need to merge this back to 60 or 59.

Status: Verified (was: Fixed)
Chrome OS 9656.0.0, 61.0.3132.0

Sign in to add a comment