New issue
Advanced search Search tips

Issue 891438 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Jan 14
Cc:
atwilson@chromium.org
igorcov@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
Chrome-Bug-Cleanup


Sign in to add a comment

New Dell Chromebook 13 3380 losing Enterprise enrollmet

Reported by chwil...@swisd.net, Oct 2 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
Platform: 10895.56.0

Steps to reproduce the problem:
1. Reset with ESC+Refresh+Power
2. 
3. 

What is the expected behavior?
Turn on and goes to log in screen

What went wrong?
Devices keep going back to set up screen

Did this work before? N/A 

Chrome version: 69.0.3497.95  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 31.0 r0

Comment 1 by ibezmenov@chromium.org, Oct 5

Labels: Needs-Feedback
Hi, thanks for reporting this, could you please provide more information about that problem (e.g. device force-enrolled, policy example, logs, etc.).

Comment 2 by emaxx@chromium.org, Oct 7

Cc: atwilson@chromium.org igorcov@chromium.org
Labels: Enterprise-Triaged
Sounds like an issue with losing enrollment due to file system corruption after a hard reboot?

Comment 3 by sylcat@google.com, Jan 11 

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Thursday, 01/17/19 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Comment 4 by kathrelk...@chromium.org, Jan 14

Status: Archived (was: Unconfirmed)
Without hearing back from the original poster (and lacking any logs about this issue), there's not much we can do here.  There are related changes between M-69 and today's stable, so hopefully this got fixed as part of another effort.

If you are still having this problem, please open another bug!
►

Sign in to add a comment