Check Failed when launching chrome with a supervised user when force sign in is enabled |
||
Issue descriptionChrome Version: M57 What steps will reproduce the problem? (1) Launch Chrome, Create a SU, close Chrome, make sure SU is the last used profile. (2) Enable Force Signin (3) Launch Chrome again What is the expected result? Because SU is not able to be signed in, UserManager should be shown. What happens instead? Check failed: profile_manager.cc(1313): Check failed: !GetProfileByPathInternal(profile_dir)
,
Dec 5 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4ea202a58ee2c14f187d219922721fe5d6bf95fc commit 4ea202a58ee2c14f187d219922721fe5d6bf95fc Author: zmin <zmin@chromium.org> Date: Mon Dec 05 18:49:01 2016 Fix Check failure in ProfileManager when force-sign-in is enabled and last used profile is supervised user BUG= 670820 BUG= 642059 Review-Url: https://codereview.chromium.org/2547083004 Cr-Commit-Position: refs/heads/master@{#436365} [modify] https://crrev.com/4ea202a58ee2c14f187d219922721fe5d6bf95fc/chrome/browser/signin/chrome_signin_client.cc [modify] https://crrev.com/4ea202a58ee2c14f187d219922721fe5d6bf95fc/components/signin/core/browser/signin_manager.cc
,
Dec 12 2016
Verified with 57.0.2949.0 canary on Win 10 |
||
►
Sign in to add a comment |
||
Comment 1 by zmin@chromium.org
, Dec 2 2016