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

Issue 715474 link

Starred by 3 users
Status: Closed
Owner:
fukino@chromium.org
Closed: Dec 11
Cc:
xiy...@chromium.org
█ dspaid@chromium.org
█ uekawa@chromium.org
hashimoto@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

Sign-in attempts get error three times after the user's cryptohome is removed.

Project Member Reported by fukino@chromium.org, Apr 26 2017 
What steps will reproduce the problem?
(1) Sign in as a new (non-owner) profile.
(2) Sign out
(3) Remove the new user's cryptohome by:
  3-1) Press Ctrl+Alt+F2 to enter VT2.
  3-2) As root, cryptohome --action=remove --user=<the new user's email>
  3-3) Back to the UI by Ctrl+Alt+F1
(4) Sign in to the new user.

What is the expected result?
The user can sign-in and the user's cryptohome is re-created.

What happens instead?
I got error "Sorry, your password could not be verified. Please try again. ..." three times. At the fourth trial, I was able to log in to Desktop.

Comment 1 by fukino@chromium.org, Apr 26 2017 

This should happen without the debug commands.
1) When a non-owner's cryptohome is removed due to low disk space.
2) When a user's cryptohome is removed due to migration failures.

Comment 2 by fukino@chromium.org, May 9 2017 

Issue 718557 has been merged into this issue.

Comment 3 by uekawa@google.com, May 9 2017

Labels: ReleaseBlock-Beta ArcExt4Crypto

Comment 4 by uekawa@google.com, May 9 2017

Labels: -ArcExt4Crypto ArcExt4Migration

Comment 5 by fukino@chromium.org, May 9 2017

Cc: uekawa@chromium.org
uekawa@, should we really block beta release?
This is a long-standing issue, and I assume issue 718557 is not related to ArcExt4Migration. (i.e. issue 718557 can reproduce without "Perform migration" step in the "Steps to Reproduce".)

Comment 6 by uekawa@google.com, May 9 2017

Labels: -ReleaseBlock-Beta

Comment 7 by fukino@chromium.org, May 9 2017 

Regarding the trigger 2) in comment 1, it was already worked around by invalidating oahth token in the migration failure screen.

Comment 8 by uekawa@chromium.org, May 17 2017 

is there anything else to be done?

Comment 9 by uekawa@google.com, May 18 2017

Labels: -M-60 -ArcExt4Migration M-61

Comment 10 by zalcorn@chromium.org, Dec 11

Status: Closed (was: Assigned)
No longer reproducible on M-72.
►

Sign in to add a comment