New issue
Advanced search Search tips

Issue 778371 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Sign-in: Unable to login to 2nd user after password change of 1st user account

Project Member Reported by sdantul...@chromium.org, Oct 25 2017

Issue description

Google Chrome	62.0.3202.74 (Official Build) beta (64-bit)
Revision	0
Platform	9901.54.0 (Official Build) beta-channel eve

What steps will reproduce the problem?
(1) Chromebook with 2 user accounts A and B
(2) Login to user A and change the account password from another machine
(3) Receive a sync error notification. Click on it to sign-out of user account
(4) No, click on user pod B

What is the expected result?
Should be able to enter password and login to user B

What happens instead?
Unable to enter password and login to user B. The user pod just flickers on click. 

Unable to reproduce this issue when there are more than 2 user accounts.

Also repro'd on samus, quawks
 
Logs and video from eve device: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/778371/


This issue is also reproducible on M61 stable 9765.85.0, 61.0.3163.123. 
Owner: jdufault@chromium.org
Status: Assigned (was: Untriaged)
Jacob any idea why this might be happening?
Cc: wzang@chromium.org
Not sure, maybe the alert is stealing focus? But this will be fixed with views-based login so probably WontFix in a little while.

Comment 4 by wzang@chromium.org, Mar 5 2018

Cc: -wzang@chromium.org jdufault@chromium.org
Owner: wzang@chromium.org
Status: Started (was: Assigned)
Will see if there's a quick fix for this.
Project Member

Comment 5 by bugdroid1@chromium.org, Mar 7 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a77ef71027dc7da26523a34f8c636492212a81ae

commit a77ef71027dc7da26523a34f8c636492212a81ae
Author: Wenzhao Zang <wzang@chromium.org>
Date: Wed Mar 07 23:08:20 2018

cros: Do not force focus for user pods without password field

It should be fine to remove the entire code path within |focusInput|
with |opt_ensureFocus| == true, since the original bug  crbug.com/725622 
was fixed by reverting another CL. However to be safe, this CL only
affects user pods without password input field.

The cause of the bug might be: when clicking the pod that requires
online sign-in (ie. the pod that does not display a password field),
the focus immediately goes to the GAIA sign-in page, so the pod never
gets the chance to remove the focus listener. When the GAIA page is
closed, the pod is still trying to steal focus. It's observed that the
issue doesn't exist if the GAIA page is not opened.

Bug:  778371 
Change-Id: Ib4f39798fa60bc0cf72bbfd67c7fe8e997f7eedb
Reviewed-on: https://chromium-review.googlesource.com/950475
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541628}
[modify] https://crrev.com/a77ef71027dc7da26523a34f8c636492212a81ae/ui/login/account_picker/md_user_pod_row.js

Comment 6 by wzang@chromium.org, Mar 7 2018

Status: Fixed (was: Started)
Status: Verified (was: Fixed)
10684.0.0, 68.0.3432.0

Sign in to add a comment