New issue
Advanced search Search tips

Issue 852745 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug


Participants' hotlists:
LoginRefresh


Sign in to add a comment

Add new user does not start session properly

Project Member Reported by rsorokin@chromium.org, Jun 14 2018

Issue description

Chrome Version: 
CHROMEOS_RELEASE_DESCRIPTION=10781.0.0 (Official Build) dev-channel lulu test
CHROMEOS_RELEASE_BOARD=lulu
Chrome	69.0.3457.0

What steps will reproduce the problem?
(1) Start with a fresh device
(2) Authenticate with a new user (not yet on the device)

What is the expected result?
Normal session start

What happens instead?
Black screen. No reaction on keyboard.

From the logs seems that session has started. After "restart ui" command I have user pod with that user on the login screen. Then login from the pod works.

I could not repro on 10779.0.0. I wonder if that was introduced by https://chromium-review.googlesource.com/c/chromium/src/+/1085635 ? 

logs attached.
 
logs.gz
130 KB Download
Labels: M-69
Owner: jdufault@chromium.org
Status: Assigned (was: Untriaged)
Unfortunately I'm unable to repro, and I don't see anything in the logs. Can you go to chrome://crashes and see if there was anything interesting there?
Hmm, I still could repro on 69.3464.0. But only with managedchrome.com account. Other accounts work fine. Could you try with yours?
Status: Started (was: Assigned)
Ah, I'm able to repro with an enterprise enrolled account.
Project Member

Comment 6 by bugdroid1@chromium.org, Jun 22 2018

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

commit e49cddab7f63fa837abe0c5ab2d055aa56532850
Author: Jacob Dufault <jdufault@google.com>
Date: Fri Jun 22 21:05:38 2018

cros: Rework LoginDisplayHostMojo::UpdateGaiaDialogVisibility

- drop LoginDisplayHost::default_host(), we're already in the default_host()
  instance
- remove early-return
- check if we're currently signing in, in which case do not show gaia (fixes the
  bug)

Bug:  852745 
Change-Id: I5e1e7dcfca2c7aca55b9301721ea3499c1a88451
Reviewed-on: https://chromium-review.googlesource.com/1110273
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569771}
[modify] https://crrev.com/e49cddab7f63fa837abe0c5ab2d055aa56532850/chrome/browser/chromeos/login/ui/login_display_host_mojo.cc
[modify] https://crrev.com/e49cddab7f63fa837abe0c5ab2d055aa56532850/chrome/browser/chromeos/login/ui/login_display_mojo.cc

Status: Fixed (was: Started)

Sign in to add a comment