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

Issue 646468 link

Starred by 3 users
Status: Verified
Owner:
█ krishna...@chromium.org
Last visit > 30 days ago
Closed: Oct 2016
Cc:
█ scunning...@chromium.org
abodenha@chromium.org
dchan@chromium.org
█ dskaram@chromium.org
█ krishna...@chromium.org
achuith@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Enterprise:Blank screen is displayed for 7-10 secs after normal and SSO enrollment

Project Member Reported by trapti@chromium.org, Sep 13 2016 
Enrollment with SSO account displays blank screen after enrollment for few secs.

Tried with trapti@crosdev3.biz

Candy 
Columns
M	ChromeOS	Chrome	ARC	Type	Channel
54	8743.25.0	54.0.2840.24	3264590	release	dev

Attaching similar screenshot for reference.
image1 (5).JPG
662 KB View Download

Comment 1 by trapti@chromium.org, Sep 13 2016 

Note: Blank screen is displayed after clicking "Done" during enrollment.

Comment 2 by trapti@chromium.org, Sep 13 2016

Cc: bartfab@chromium.org
Owner: bartfab@chromium.org
@bartfab please reassign to the right person

Comment 3 by tnagel@chromium.org, Sep 13 2016

Cc: -tnagel@chromium.org

Comment 4 by trapti@chromium.org, Sep 15 2016

Labels: ReleaseBlock-Stable

Comment 5 by trapti@chromium.org, Sep 16 2016 

At times blank screen seen during normal enrollment process too

Comment 6 by trapti@chromium.org, Sep 16 2016 

Blank Screen for few sec also seen in normal enrollment after Done button response

Peppy

M	ChromeOS	Chrome	ARC	Type	Channel
54	8743.28.0	54.0.2840.25	3268846	release	dev

Comment 7 by trapti@chromium.org, Sep 16 2016

Summary: Enterprise:Blank screen is displayed for 7-10 secs after normal and SSO enrollment (was: Enterprise:Blank screen is displayed for 7-10 secs after SSO enrollment)

Comment 8 by scunning...@chromium.org, Sep 20 2016

Cc: dskaram@chromium.org
Status: Assigned (was: Available)

Comment 9 by dskaram@chromium.org, Sep 21 2016

Cc: -bartfab@chromium.org abodenha@chromium.org
Owner: achuith@chromium.org
This seems really similar to the other bug where actions are taking too long. Assigning to Achuith as well so he can route both bugs accordingly.

Comment 10 by achuith@chromium.org, Oct 3 2016

Cc: achuith@chromium.org
Owner: krishna...@chromium.org
Krishna: Is this still happening?

Is this a dupe of  crbug.com/646460 ?

Comment 11 by trapti@chromium.org, Oct 3 2016

Status: Verified (was: Assigned)
Am not able to repro this anymore. Will reopen if this occurs again.

Lulu
M	ChromeOS	Chrome	ARC	Type	Channel
54	8743.52.0	54.0.2840.48	3320691	release	beta
Project Member

Comment 12 by blocker...@chrome-infra-auth.iam.gserviceaccount.com, Oct 28 2016

Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-54; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-54 label, otherwise remove Merge-TBD label. Thanks.
Project Member

Comment 13 by sheriffbot@chromium.org, Dec 12 2016

Labels: -Merge-TBD
►

Sign in to add a comment