Guido, can we have someone take a look at this? Two things stuck out:

1) In the video, one device didn't sign out the user immediately.
2) The devices get stuck at the splash screen and never get to display the "device disabled" UI.

Igor and Bartosz have some context for how this works and can help with diagnostics.

(1) looks like the push message is not getting through immediately. The video was uploaded 9 days ago, I fear server-side logs may be gone already. But you could reach out to Dennis to check whether he can find out any traces of push messages sent to these two serial numbers.

(2) looks like a definite client-side bug. Next step would be to try and repro, to find out where it is hanging. The device should boot normally, but then show the disabled screen on top of the login screen.

Guys, do we have any updates for this issue? My customer needs an update but I can get more information from him if needed.

I got a customer with this issue as well. He is using Lenovo 100e Chromebooks on the stable channel. I was also able to reproduce it on a Dell 13 7310 in beta.

Shortly after receiving the disable message the device crashes and reboots and gets stuck in a bootloop. When I tried to do it from a public session I reloaded the policies from the browser and a notification popped up that mentioned a partition that could not be mounted, then it went into the bootloop again. The only way out is to powerwash it.

++case 17322226 
When enabling disabled device, it goes to white screen with chrome logo.
When disabling back, it goes to disabled state as expected.

Last policy fetch is today.
69.0.3497.120 reks
No public sessions is enabled.

Have reliable repro steps

1. In Admin Console in Device settings set Sign-in Language to "English (New Zealand).
2. Navigate to chrome://policy, refresh, make sure it receives DeviceLoginScreenLocales as en-NZ
3. Disable device
4. Observe chrome logo on white background.

Logs with segfault message:
https://drive.google.com/drive/folders/1dNMfiPZd9v-ryeIgmdyT1rpNAYoZjFUv?usp=sharing

Attached 
2018-11-13T22:15:27.405745+00:00 INFO kernel: [  275.427860] chrome[8582]: segfault at 0 ip 000057bd2859f6e7 sp 00007ffef6a76bc8 error 4 in chrome[57bd269f4000+87cc000]
2018-11-13T22:15:27.415957+00:00 INFO crash_reporter[8751]: libminijail[8751]: mount /dev/log -> /dev/log type ''
2018-11-13T22:15:27.432507+00:00 WARNING crash_reporter[8751]: [user] Received crash notification for chrome[8582] sig 11, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2018-11-13T22:15:27.448964+00:00 INFO session_manager[8556]: [INFO:child_exit_dispatcher.cc(59)] Handling 8582 exit.
2018-11-13T22:15:27.448987+00:00 ERR session_manager[8556]: [ERROR:child_exit_dispatcher.cc(67)]   Exited with signal 11
2018-11-13T22:15:27.449008+00:00 INFO session_manager[8556]: [INFO:session_manager_service.cc(297)] Exiting process is chrome.
2018-11-13T22:15:27.449022+00:00 INFO session_manager[8556]: [INFO:browser_job.cc(157)] Terminating process group: Ensuring browser processes are gone.
2018-11-13T22:15:27.449038+00:00 INFO session_manager[8556]: [INFO:system_utils_impl.cc(94)] Sending 9 to -8582 as 1000
2018-11-13T22:15:27.454928+00:00 INFO session_manager[8556]: [INFO:browser_job.cc(148)] Running child /opt/google/chrome/chrome --ppapi-flash-path=/opt/google/chrome/pepper/libpepflashplayer.so --ppapi-flash-version=30.0.0.134 --ui-prioritize-in-gpu-process --use-gl=egl --enable-native-gpu-memory-buffers --enable-webgl-image-chromium --enable-features=Pepper3DImageChromium --gpu-sandbox-failures-fatal=yes --enable-logging --log-level=1 --use-cras --enable-wayland-server --user-data-dir=/home/chronos --system-developer-mode --login-profile=user --has-chromeos-keyboard --enable-touchview --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --child-wallpaper-large=/usr/share/chromeos-assets/wallpaper/child_large.jpg --child-wallpaper-small=/usr/share/chromeos-assets/wallpaper/child_small.jpg --default-wallpaper-large=/usr/share/chromeos-assets/wallpaper/default_large.jpg --default-wallpaper-small=/usr/share/chromeos-assets/wallpaper/default_small.jpg --arc-availability=officially-supported --enterprise-enrollment-initial-modulus=15 --enterprise-enrollment-modulus-limit=19 --login-manager --vmodule=*arc/*=1,*chromeos/login/*=1,auto_enrollment_controller=1,*/ui/ozone/*=1,*/ui/display/manager/chromeos/*=1,*night_light*=1,power_button_observer=2,webui_login_view=2,lock_state_controller=2,webui_screen_locker=2,screen_locker=2 --enable-features=Pepper3DImageChromium --show-webui-login
2018-11-13T22:15:28.104574+00:00 WARNING crash_reporter[8814]: Received crash notification for chrome[8754] user 1000 (called directly)
2018-11-13T22:15:28.106830+00:00 ERR crash_reporter[8814]: Could not get active user sessions, using default.
2018-11-13T22:15:28.149958+00:00 INFO session_manager[8556]: [INFO:child_exit_dispatcher.cc(59)] Handling 8814 exit.

Chrome OS has two sets of locales:
* All locales (e.g. en-NZ, en-AU, ...)
* UI locales (e.g. en-US, en-GB, ...)

The former define keyboard layouts, timezone settings, etc. and defer for the latter for UI strings (e.g. en-NZ, en-AU, en-GB very likely all use the same en-GB strings in the UI).

It looks like we may be confusing the typ types of locales here - we are trying to look up strings in en-NZ, which do not exist.

I think Zakhar recently touched UI locales code.
Will you be able to try to reproduce it and figure out what crashes?

Hello team,

We're looking for more updates on this bug. Was the issue reproduced? We have this case #16873261 where the issue is still experienced as well

Hi, I've reproduced the bug, however couldn't get anything useful from logs yet. I'll look deeper into this tomorrow.

Hi All,

We are the original reporter of this bug.
Checking in for further updates, and if there is anything further we can assist with to determine the cause.

So far, we can offer workaround: set Sign-in Language to "English (United States)".

Hi Team,

I asked my customer to test the work around by changing the Sign-in Language to "English (United States)", but this didn't work for him. The previous region indicated on the policy was New Zealand.

Any insight? 

Thanks in advance!

Hello Team,

Following the work around didn't work on my customer's end, they are from NZ. Same issue has been experienced. 

Is there any updates about the issue?

Thanks!

@poromov, could you take another look at this, please.

I was able to reproduce this bug without setting "LoginScreenLocales" policy. So, it's probably not related to my changes for UI locales.

Once the chromebook was disabled, every time you launch it, the chrome process goes into a crash loop, leaving a new log file once a couple of seconds. Couldn't get any crash reports for my local setup though.

Commenting out this line makes the crash go away (along with the "disabled" screen):

https://cs.chromium.org/chromium/src/chrome/browser/chromeos/system/device_disabling_manager_default_delegate.cc?type=cs&q=DeviceDisablingManagerDefaultDelegate&sq=package:chromium&g=0&l=22

I don't know who is the right person to reassign it to.

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Hello team,

We have another affected domain under case #18028709 


The customer is experiencing the issue described in crbug.com/884127, however, the proposed solution does not work for him. The issue is happening even with English US locale. It's been happening randomly to their devices. During tests some of them went into the bootloop and some didn't. 

Example serial numbers: 
172FB52 - Bootloop 
HJZFB52 - Bootloop 
81KQ3H2 - Unaffected 

Repro steps: 

1. Disable the device from the device management page 
2. Device crashes and goes into a bootloop 
3. According to the crbug it can be reproduced reliably by changing the Sign-in language to English NZ or AU but in this customer's case it happens even with English US locale. 

Log files from device 172FB52. May or may not be useful since the only solution is to wipe and re-enroll the device 
https://drive.google.com/file/d/1FyVHcGKwUYO-ejq31oyZkGAtzRHD4ozi/view?usp=sharing

According to #16 it looks like Chrome crashes at some moment after going into disabled screen.

Anatoliy, could you please track down where actually the crash happens?