Issue metadata
Sign in to add a comment
|
Enterprise:No sign in screen seen after Public Session is disabled.It's seen after reboot. |
||||||||||||||||||||
Issue descriptionDaisy/Peppy Columns M ChromeOS Chrome ARC Type Channel 54 8743.28.0 54.0.2840.25 3268846 release dev Enroll device with Public Session Enabled Disable Public Session Expected:Sign in screen should display Actual: No sign in screen appears and no response on clicking add person or Apps button.Only after reboot,sign in screen is displayed
,
Sep 19 2016
I don't fully understand the bug. You should still see an add person button even if there is a public sessions enabled. What are you seeing if you do not disable public sessions? Is this a regression? If so can we do a bisect, if this is really a stable blocker?
,
Sep 19 2016
@atwilson Yes this is Regression.As expected when Public Session is disabled then sign in screen should be displayed,which is now seen after rebooting.Could you try to repro this and look into this.
,
Sep 19 2016
Could be interlinked to https://bugs.chromium.org/p/chromium/issues/detail?id=647082.
,
Sep 20 2016
Trapti can you do a bisect since this is a regression?
,
Sep 20 2016
Since reboot resolves, lowering priority. We don't have the bandwidth to help bisect.
,
Sep 21 2016
OK, sounds like this isn't a release blocker then. If you guys get cycles to help bisect, that's be super helpful, but agreed that there are higher priority issues.
,
Sep 21 2016
Peppy Columns M ChromeOS Chrome ARC Type Channel 54 8743.35.0 54.0.2840.33 3284275 release beta Note:No user has signed in.It's just enrolled device with no user signed in.
,
Nov 11 2016
,
Dec 21 2016
@sduraisamy, please review and update the labels accordingly. Removing the Milestone label for now. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by sduraisamy@chromium.org
, Sep 15 2016