Issue metadata
Sign in to add a comment
|
Pin unlock: Unable to choose 'PIN or password' setting on eve. |
||||||||||||||||||||||
Issue descriptionGoogle Chrome 68.0.3440.70 (Official Build) beta (64-bit) Revision dcbf48aee0a261c062487bf346c0dbbd4f346a06-refs/branch-heads/3440@{#718} Platform 10718.58.0 (Official Build) beta-channel eve What steps will reproduce the problem? 1. Open Settings -> Screen lock and sign-in section 2. Enter password for the user account 3. Select 'PIN or password' option 4. Click on 'Set up PIN' button, configure PIN and click on 'Confirm' button 5. Press 'Search + L' and observe lock screen. What is the expected result? Lock screen should display PIN unlock option What happens instead? Lock screen does not display PIN unlock option. Also, after selecting 'PIN or password' option, click on back button and open Screen lock section again. Note that setting is reset to 'Password' option. Issue not reproduced on kevin and veyron_minnie on the same build.
,
Jul 20
First, to check if Pinweaver can be involved: PinWeaver is not supported in M68-10718.58.0 on eve. However, it is controlled by the cr50 image installed. If a recent M69 was installed on that machine, and then it went back to M68, a cr50 with PinWeaver support could have been installed (and then it doesn't rollback to earlier versions). What does cr50_version say in chrome:system. If RW line in cr50_version says 0.3.7, then PinWeaber is there and it might be a dup of issue 863572. If that line says 0.3.4, it must be some UI issue.
,
Jul 20
c50_version: RO 0.0.10 RW 0.3.7
,
Jul 20
Ok, PinWeaver is enabled. 1) That's not the cr50 version that is supposed to go with M68. You may want to rollback manually on that device to test M68 there. 2) And it's likely a dup of issue 863572. Or, something related to issue 863475 .
,
Jul 20
sdantuluri@, could you please post logs / feedback report to check if it's indeed issue 863572?
,
Jul 20
I just performed an auto-update to M69 and did a rollback to M68 to test the pin unlock again. The pin unlock works fine now. Able to see PIN unlock on lock screen. cr50_version is still the same. RO 0.0.10 RW 0.3.7
,
Jul 20
Put the system to sleep for 30+ seconds, or better a couple minutes to make sure cr50 went into deep sleep (if you have a test image, can do powerd_dbus_suspend --wakeup_timeout=30) and check if PIN still works after that.
,
Jul 20
Note that rollback to M68 doesn't rollback cr50 image to the one distributed with M68 (by design, you can't downgrade cr50 version - that's only possible with special dev images manually).
,
Jul 20
Re c#7. PIN unlock is working fine after suspend/resume of device
,
Jul 23
Is this all WAI and we can close it? This is marked as a stable blocker for 68 so we need to clear it.
,
Jul 23
Yes. We can close this bug. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sdantul...@chromium.org
, Jul 20