Mobile data is shown Initializing status even though no mobile is available |
||||||||
Issue descriptionChrome Version: (copy from chrome://version) OS: ChromeOS M65.0.3325.65 10323.30.0 beta candy What steps will reproduce the problem? (1) Sign in on an enrolled device connected to WiFi and has no mobile option. (2) Click on Uber tray and expand the Network tab. What is the expected result? Network tab is shown showing only a list of Wifi network. Mobile data should be hidden like in non-enrolled consumer device state. What happens instead? Mobile data section is shown with the switch is disabled and grayed out. Showing this section with the proper status might be fine but since M65, showing a "Initializing..." status is incorrect and confusing. In M63.0.3239.140 10032.86.0 stable Speedy, the status is "No mobile network available". In M64.0.3282.167 10176.72.0 stable daisy, no status is shown. In M65.0.3325.65 10323.30.0 beta candy and M66.0.3344.0 10421.0.0 dev pit, the status is "Initializing".
,
Feb 27 2018
Can you show the Settings UI while in this state? Does 'Initializing' eventually go away? This sounds like it might be aTether issue?
,
Feb 27 2018
Can you clarify what you mean by "enrolled" and "non-enrolled" devices? Does the Candy device have a cellular (LTE) modem? Can you please navigate to chrome://proximity-auth and provide the logs there?
,
Feb 27 2018
,
Feb 27 2018
This still needs triage. I doubt it is enterprise enrolled per-se, I suspect that enterprise enrollment may be making Tether available but we need more info.
,
Feb 27 2018
khorimoto@ Enrolled device = managed device under control by Enterprise device policies Non-enrolled device = consumer device not managed by Enterprise device policies None of the devices I mentioned have a cellular modem. To avoid managed-user policies in the variables, I used a standard Gmail account to compare the behaviors of a managed (enrolled/Enterprise) device and an unmanaged (non-enrolled/consumer) device. Both tests were run on the same device but at slight different time apart. Please find the logs and screenshots in: https://drive.google.com/drive/folders/1-r31Lk3cKQiUMojaVn7IFDzFJg75mCHx?usp=sharing
,
Feb 27 2018
stevenjb@ the "Initializing" status stays indefinitely not going away.
,
Feb 27 2018
Steven, I believe this is caused by your CL: https://chromium-review.googlesource.com/c/chromium/src/+/738910/1/ash/system/network/network_list.cc#339 See my comment: "AFAIK, the UX designers do not want any Cellular initialization subtitle if Cellular is unavailable. Can you double-check with elizabethchiu@ and/or shibasheikh@?" This is the only time that "Initializing" will ever be shown if State(Cellular) == TECHNOLOGY_UNAVAILABLE.
,
Dec 13
Bulk-assigning unassigned status area bugs to me.
,
Dec 13
,
Dec 20
++ support case 17833496 where no physical modem is present on candy (only slot for modem closed with hex bit): But have following in log: "2018-12-18T13:23:29.066214-05:00 INFO ModemManager[1093]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0': not supported by any plugin" And cellular connection is always shown as "initializing".
,
Dec 20
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by pastarmovj@chromium.org
, Feb 27 2018Components: UI>Shell>Networking UI>Shell>StatusArea
Labels: Enterprise-Triaged