Hi all,

Same behavior is also observed on version 60. Thanks!

Krishna, can we repro it? Looks like an issue with Network config dialog and VK. Thanks.

We are experiencing a similar issue with Asus Chromebits (model: B013C) and wireless mouse/keyboards (model: LYNEC C120) in approximately 1 out of 5 devices. Steps to reproduce:
1) Connect and enroll the device into our default organization which has a Kiosk App but no WiFi network configured on it
2) restarting the device
3) bypassing the Kiosk App
4) logging into the Chromebit with the user that enrolled the device
5) forgetting the network
6) sign out and restart

Google Chrome Versions on devices this issue was observed on: 59.0.3071.113, 59.0.3071.134
Platform Version: 9460.67.0 (Official Build) stable-channel veyron_mickey, 9460.73.1 (Official Build) stable-channel veyron_mickey
Firmware Version: Google_Veyron_Mickey.6588.264.0

Thanks!
Asaf

One quick follow-up: we plugged in a USB mouse and experienced the same issue, so it doesn't appear to be related to the type of mouse/keyboard.

I was able to reproduce the problem on a sumo, M-59 Stable build 9460.76.0, chrome 59.0.3071.135 and saw the same problem as described for 59.0.3071.134 (the select list closes and no button is active after that).

After plugging a keyboard and mouse back in the mouse could move around, but clicks on the network select list and other buttons had no effect.

rkc@, can you help triage?

59.0.3071.135 where wifi config dialog does not show up is issue 727951

Xiyuan, looks like this is related to the Network Config UI issue that you are handling.

https://bugs.chromium.org/p/chromium/issues/detail?id=752440

For the keyboard issue, it only happens with virutal keyboard. Physical keyboard works as expected.

VK is probably broken on the app launch splash screen for quite sometime (or never worked). The reason it does not work is because we deactivate IME in the signin profile after app profile is loaded. However, when network config UI is shown, the login screen will be held active and ash still uses the VK from the signin profile. Since IME from signin profile is deactivated, VK would not generate any key events.

So, it is an issue for a while now? 

Yes, I believe the problem has been there for quite a while. The code to activate user (app) profile IME engine is at least two years old.

Proposed fix out for review:
https://chromium-review.git.corp.google.com/c/608837

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fbf724f01d4569314087d0bf8a0a9b46dc883087

commit fbf724f01d4569314087d0bf8a0a9b46dc883087
Author: Xiyuan Xia <xiyuan@chromium.org>
Date: Wed Aug 09 20:20:48 2017

kiosk: Reset virtual keyboard after app profile load

Sign-in profile's IME engine is disabled after app profile
finishes loading. As a result, existing virtual keyboard
built from sign-in profile will stop functioning. This is
usually fine since the virtual keyboard will be reset
after app session starts (session state changes to ACTIVE).
However, it would be a problem when virtual keyboard is used
before session state change such as in the kiosk network config
case. The CL fixes the problem by resetting the virtual keyboard
after app profile is loaded to cover the time after app profile
is loaded but before app session starts.

BUG= 748432 

Change-Id: I67b332bb2331dc818c0891f1753cddf4a55b1e4f
Reviewed-on: https://chromium-review.googlesource.com/608837
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#493121}
[modify] https://crrev.com/fbf724f01d4569314087d0bf8a0a9b46dc883087/chrome/browser/chromeos/login/app_launch_controller.cc

Removing M59 tag since there is no more release on it.

Requesting merge to M61 and M60.

ok, discussed with Xiyuan to confirm this is minimum impact and scope is limited to Kiosk 

Approved for M60, we should also merge to M61 (approved there too)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c5a236ecb204204faf4794f7e4e0d9fafc849671

commit c5a236ecb204204faf4794f7e4e0d9fafc849671
Author: Xiyuan Xia <xiyuan@chromium.org>
Date: Thu Aug 10 20:27:11 2017

Merge M61 "kiosk: Reset virtual keyboard after app profile load"

> Sign-in profile's IME engine is disabled after app profile
> finishes loading. As a result, existing virtual keyboard
> built from sign-in profile will stop functioning. This is
> usually fine since the virtual keyboard will be reset
> after app session starts (session state changes to ACTIVE).
> However, it would be a problem when virtual keyboard is used
> before session state change such as in the kiosk network config
> case. The CL fixes the problem by resetting the virtual keyboard
> after app profile is loaded to cover the time after app profile
> is loaded but before app session starts.
>
> BUG= 748432 
>
> Change-Id: I67b332bb2331dc818c0891f1753cddf4a55b1e4f
> Reviewed-on: https://chromium-review.googlesource.com/608837
> Reviewed-by: Toni Barzic <tbarzic@chromium.org>
> Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#493121}
> (cherry picked from commit fbf724f01d4569314087d0bf8a0a9b46dc883087)

TBR=xiyuan@chromium.org

Change-Id: I358ea4181446da25c23f7c4afab1c54b9f13f232
Reviewed-on: https://chromium-review.googlesource.com/611051
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/branch-heads/3163@{#455}
Cr-Branched-From: ff259bab28b35d242e10186cd63af7ed404fae0d-refs/heads/master@{#488528}
[modify] https://crrev.com/c5a236ecb204204faf4794f7e4e0d9fafc849671/chrome/browser/chromeos/login/app_launch_controller.cc

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/84ce6bd512a7be7e3ff383e70ac4c244a4b855ad

commit 84ce6bd512a7be7e3ff383e70ac4c244a4b855ad
Author: Xiyuan Xia <xiyuan@chromium.org>
Date: Thu Aug 10 20:29:30 2017

Merge M60 "kiosk: Reset virtual keyboard after app profile load"

> Sign-in profile's IME engine is disabled after app profile
> finishes loading. As a result, existing virtual keyboard
> built from sign-in profile will stop functioning. This is
> usually fine since the virtual keyboard will be reset
> after app session starts (session state changes to ACTIVE).
> However, it would be a problem when virtual keyboard is used
> before session state change such as in the kiosk network config
> case. The CL fixes the problem by resetting the virtual keyboard
> after app profile is loaded to cover the time after app profile
> is loaded but before app session starts.
>
> BUG= 748432 
>
> Change-Id: I67b332bb2331dc818c0891f1753cddf4a55b1e4f
> Reviewed-on: https://chromium-review.googlesource.com/608837
> Reviewed-by: Toni Barzic <tbarzic@chromium.org>
> Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#493121}
> (cherry picked from commit fbf724f01d4569314087d0bf8a0a9b46dc883087)

TBR=xiyuan@chromium.org

Change-Id: I35c21a7f2b18b10a98a13c69189ae422902c8b8e
Reviewed-on: https://chromium-review.googlesource.com/611053
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/branch-heads/3112@{#719}
Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}
[modify] https://crrev.com/84ce6bd512a7be7e3ff383e70ac4c244a4b855ad/chrome/browser/chromeos/login/app_launch_controller.cc

CL caused a regression (issue 756191). :(

Per discussion with sduraisamy@, let's revert it on M60 and merge the follow up fix in M61 with issue 756191.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b73aaa14d8c9aab3699226e6d9c4606c476ffb9c

commit b73aaa14d8c9aab3699226e6d9c4606c476ffb9c
Author: Xiyuan Xia <xiyuan@chromium.org>
Date: Mon Aug 21 17:57:53 2017

Revert "Merge M60 "kiosk: Reset virtual keyboard after app profile load""

This reverts commit 84ce6bd512a7be7e3ff383e70ac4c244a4b855ad.

Reason for revert: Caused new regression http://crbug.com/756191

Original change's description:
> Merge M60 "kiosk: Reset virtual keyboard after app profile load"
> 
> > Sign-in profile's IME engine is disabled after app profile
> > finishes loading. As a result, existing virtual keyboard
> > built from sign-in profile will stop functioning. This is
> > usually fine since the virtual keyboard will be reset
> > after app session starts (session state changes to ACTIVE).
> > However, it would be a problem when virtual keyboard is used
> > before session state change such as in the kiosk network config
> > case. The CL fixes the problem by resetting the virtual keyboard
> > after app profile is loaded to cover the time after app profile
> > is loaded but before app session starts.
> >
> > BUG= 748432 
> >
> > Change-Id: I67b332bb2331dc818c0891f1753cddf4a55b1e4f
> > Reviewed-on: https://chromium-review.googlesource.com/608837
> > Reviewed-by: Toni Barzic <tbarzic@chromium.org>
> > Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#493121}
> > (cherry picked from commit fbf724f01d4569314087d0bf8a0a9b46dc883087)
> 
> TBR=xiyuan@chromium.org
> 
> Change-Id: I35c21a7f2b18b10a98a13c69189ae422902c8b8e
> Reviewed-on: https://chromium-review.googlesource.com/611053
> Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
> Cr-Commit-Position: refs/branch-heads/3112@{#719}
> Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}

TBR=xiyuan@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Change-Id: I68546cffdf7495c06420d418c1471dc2356876ec
Reviewed-on: https://chromium-review.googlesource.com/623588
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/branch-heads/3112@{#740}
Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}
[modify] https://crrev.com/b73aaa14d8c9aab3699226e6d9c4606c476ffb9c/chrome/browser/chromeos/login/app_launch_controller.cc

Removing M60 label since the fix is no longer targeted for it.

Attempted to verify on M-61 Beta build 9765.72.0, chrome 61.0.3163.108, but was not successful.

Device:  Sumo (aka AOpen Chromebase)

I started with a wired ethernet connection and a keyboard attached.  At the sign-in screen I went to Settings, Accessibility, and enabled the on-screen keyboard.  

Enterprise-enrolled the device to the crosprqa4.com domain, and assigned it to an Org. Unit (Operations > Facilities) which auto-launches chrome sign builder and requires a network connection to reach a YouTube URL.  It auto-launched and played fine.

Disconnected the ethernet and keyboard.  Rebooted.
Chrome Sign Builder's splash screen appeared for 3 seconds and then:

       [dinosaur icon]
       There is no Internet connection
       Try:
          * Checking the network cables, modem and router
          * Reconnecting to Wi-Fi
          * Running Connectivity Diagnostics [highlighted]

The connectivity diagnostics line would be grey-lighted when touched, but did not have any observable effect.

Rebooted the device.  Same thing.  Rebooted 10 times and it never brought up a network selection dialog box.

Out of desperation I reattached the keyboard and typed ctrl+alt+n at the auto-launch and the network selection box appeared.  I disconnected the keyboard again.  I selected the Google-A wifi network by touch which requires a user id and password to connect.  Touching the user id text box showed a blue raindrop pointer, but no virtual keyboard popped up to enter the id.   I reconnected the keyboard and it was able to enter a user id.

(I am kicking myself...)

Virtual Keyboard has to be enabled in Cpanel for the kiosk app as well as on the device.  Retrying.

Retry details:

Sumo, with M-61 Beta build 9765.72.0, chrome 61.0.3163.108 installed.
During OOBE, System Settings > Accessibility > On-screen keyboard enabled.
Enterprise-enrolled the device to domain crosprqa4.com.
Assigned to Org. Unit "Virtual Keyboard", which auto-launches Chrome Sign Builder to play a YouTube URL that has a text entry search bar.
The CSB app for the Org. Unit has the "Disable Virtual Keyboard" slider off (i.e., Virtual Keyboard is allowed).

Disconnected the physical keyboard, but kept the ethernet connection.
Rebooted the device.  CSB auto-launched, I touched the Search bar and a virtual keyboard popped up as expected.

Disconnected the ethernet cable and rebooted.
CSB tried to launch, but "There is no Internet connection".
Rebooted another five times, but never got the Network Selection dialog bbx.

Reconnected the physical keyboard, rebooted, ctrl+alt+n at the app launch, and got the Network Selection box.  Disconnected the keyboard, touch-selected Google-A wifi, and got a virtual keyboard to enter a user id and password.

So, there is still a problem getting the Network Selection dialog to show up when the ethernet cable is removed, but once it does the Virtual Keyboard works fine.

> Disconnected the ethernet cable and rebooted.
> CSB tried to launch, but "There is no Internet connection".
> Rebooted another five times, but never got the Network Selection dialog bbx.

Can you check whether "DeviceLocalAccountPromptForNetworkWhenOffline" policy is set to false for the device? 

https://www.chromium.org/administrators/policy-list-3#DeviceLocalAccountPromptForNetworkWhenOffline

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 Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.