Hi, another enterprise customer is having the same issue in PS and on the Login screen on buddy devices.

ChromeOS:57.0.2987.137
Multiple devices?: yes
Multiple users?: yes

Domain/SN/SupportCase# is available:
https://docs.google.com/a/google.com/document/d/1bhrODPovnRQ3WgS5EeDXLigTu5MlEJiD5fByQL5Wq68/edit?usp=sharing

Troubleshoot already taken:
- Confirmed that [Device Settings] > [Accessibility Control] > ["Turn off accessibility settings on sign-in screen upon logout"] is unchecked (= Use Accessibility Control)
- Policy has been fetched successfully.
- Issue persists on the login screen 
- Issue persists in Public Session 
- Issue persists in User Session

Workaround 
- Turn on "On-screen Keyboard" from Settings > Accessibility menu, but this workaround is not reasonable for the customer as they use PS.

Debug logs:
https://drive.google.com/a/google.com/file/d/0B8hJbBKk0-c4ZFhsbzNLRndwUzQ/view?usp=sharing

I changed the priority to pri-1, as buddy is touch-panel model and this issue would affects to all users who uses buddy.

Hi there,

Is there any update on this?
Thank you!

Albert/Andrew, would this be something on either of your teams?

Is there an update?

We just rolled out Acer Chromebase 24's as survey kiosks.  Users are unable update free form text areas.  There is no onscreen keyboard.  

Devices that have not updated to 57 are working fine.

Friendly ping, is any updates on this?

I can reproduce the issue on buddy device.

- Issue persists on m57 (stable) and m58 (beta)
- Issue persists on guest mode/User session/Public session
- Issue doesn't happens on m56 (9000.92.0, 56.0.2924.112) on the same device.

- Issue happens on multiple models, multiple domains (Comment#1 and Comment#6 are different customers + we can reproduce it).

Workaround
- Turn on the On-screen keyboard form Accessibility control settings (it it doesn't exists, admins should enable it), the on-screen keyboard will be shown in Guest/PS. (For user session, we should turn on it again after the log-in)

- Use the old (<m56) recovery stick and pinned the cros version to m56. 

Watch point
- No workaround for kiosk devices (as there is no on-screen keyboard).

Hi. I'll like to look into this issue, but don't have a Buddy device. I've ordered a Buddy device, but not sure how long does it take to be delivered.
Do you know if the issue reproduces on Panther, which I have?

 Issue 718147  has been merged into this issue.

Reproduced using Buddy.

We can reproduce this problem on the AOpen Chromebase.

We have a kiosk application which was working fine for M56. On M57 and M58 the onscreen keyboard fails to appear for Text or Numeric fields.

This kiosk is deployed in multiple retail outlets, and now they are unable to do the job they've been put there to do.

Let's prioritize this fix above all other VK work at the moment as it's affecting multiple customers in stable.

Testing using Buddy 9202.54.0  57.0.2987.115 (the issue reproduces).

I found NOTREACHED log from https://cs.chromium.org/chromium/src/ui/display/manager/display_manager_utilities.cc?q=display_manager_utilities&sq=package:chromium&dr=C&l=5

Oshima-san, on Buddy, NOTREACHED is hit inside GetScalesForDisplay. Does it look a serious issue? (I'm investigating the issue that VK doesn't show up on Buddy.)

ShowKeyboardInternal is not called. The method is called for a11y keyboard.

Will bisect tomorrow.

#17 might be wrong.

good: 56.0.2924.112  9000.92.0

good: 56.0.2884.0  9000.92.0

good: 57.0.2926.0  9000.92.0

bad: 	9202.56.1	57.0.2987.123

good: 	9015.0.0	57.0.2926.0

good: 9113.0.0	57.0.2959.0

good:	9153.0.0	57.0.2970.0

good:	9173.0.0	57.0.2978.0

good:	9173.0.0	57.0.2978.0
bad:	9187.0.0	57.0.2982.0

chrome logs: https://chromium.googlesource.com/chromium/src/+log/57.0.2978.0..57.0.2982.0?pretty=fuller&n=10000
cros logs: https://crosland.corp.google.com/log/9173.0.0..9187.0.0

good:	9178.0.0	57.0.2978.0
bad:	9187.0.0	57.0.2982.0

chrome logs: https://chromium.googlesource.com/chromium/src/+log/57.0.2978.0..57.0.2982.0?pretty=fuller&n=10000
cros logs: https://crosland.corp.google.com/log/9178.0.0..9187.0.0

good:	9178.0.0	57.0.2978.0
bad	9183.0.0	57.0.2980.0

chrome logs: https://chromium.googlesource.com/chromium/src/+log/57.0.2978.0..57.0.2980.0?pretty=fuller&n=10000
cros logs: https://crosland.corp.google.com/log/9178.0.0..9183.0.0

oka@ go to sleep. It's a Saturday :) 

good:	9178.0.0	57.0.2978.0
bad:	9182.0.0	57.0.2978.0

chrome logs: https://chromium.googlesource.com/chromium/src/+log/57.0.2978.0..57.0.2980.0?pretty=fuller&n=10000
cros logs: https://crosland.corp.google.com/log/9178.0.0..9182.0.0

This is the smallest range in terms of Chrome OS version, and there are still several hundreds of CLs in the range. I'll continue to invesigate it in the next week.

In bad case, Chrome crashes when a physical keyboard is connected via USB and removed. Stack trace:

[3803:3803:0513/011607.681811:ERROR:display_manager_utilities.cc(69)] NOTREACHED() hit.
[3803:3803:0513/011608.942688:ERROR:display_manager_utilities.cc(69)] NOTREACHED() hit.
[3803:3841:0513/012317.917903:FATAL:libc_close_tracking.cc(147)] Failed to close a fd, attach info to http://crbug.com/660960, fd=121, errno=19, stack=0x6091757f89ab 0x7984bbaaf382 0x7984bbaae93d 0x7984bbaae965 0x7984bbaac584 0x7984bbaab856 0x7984bbaabc0b 0x7984bbaa42ef 0x7984bbaa9ac4 0x7984bbaa959b 0x7984bbaa9779 0x7984bba9f4a1 0x7984bbaa06e5 0x609177afeb53 0x60917580575c 0x609175823e36 0x6091758053ef 0x609177171258 0x609176e508f6 0x609176495b6b 0x609176498835 0x6091764929dc 0x609176df139a 0x609176df003b 0x609175a825bb 0x7984be335796 0x609175a823d9
_sys_cr_finished
System crash-reporter failed to process crash report.
Report Id:
[4917:4917:0513/012318.548617:ERROR:display_manager_utilities.cc(69)] NOTREACHED() hit.

The crash you saw is probably fixed in sub bug ( issue 681865 ) of issue 660960.

This fix is CL https://codereview.chromium.org/2639043002. For M57, it is included in 57.0.2986.0 (or above).

Official M57 is branch 2987, why we are looking at old branches 2978 etc ?

Thank you. I confirmed that the crash has been fixed in (60.0.3099.0).
However VK still doesn't appear; that is a different issue from the crash.

hi,

we built / found a workaround by force enabling VK via accessibilityFeatures API on app load.

this is obviously only applicable if the app is only used on touch, or if the vendor builds in more comprehensive logic to activate selectively/configuration based.

seems like the built in equivalent for some of these touch displays might not get kicked off? - an area/function worth investigating. 

interestingly enough, the convertible books (ie asus c302) seem to work fine - anything changed specific to those devices that might have such effect?

not sure if this helps finding a 'cause', but might be an area or two worth looking into.

From #31, the culprit should be in Chrome OS, not in Chrome.
cros logs: https://crosland.corp.google.com/log/9178.0.0..9182.0.0

The culprit should be in third_party/chromiumos-overlay

I checked out the bad revision 9182.0.0 -> No VK appears
Reverted src/platform2 -> No VK appears
Reverted third_party/chromiumos-overlay -> VK appears

Bisect says this is the first bad commit.

udev: unmask 225
https://chromium-review.googlesource.com/c/409017/

I ran lsusb and lspci in both good and bad images, but there is no diff.

+mka@

Matthias. Your change looks caused the issue that virtual keyboard does not appear on buddy devices. Could you take a look?

The change is: udev: unmask 225
https://chromium-review.googlesource.com/c/409017/

My wild guess is the device mistakenly thinks that a physical keyboard or alike is connected, but not sure.

Can you revert the change? Though I couldn't simply revert it on ToT with the errors include the following:

udev-208-r7: ../systemd-208/src/udev/mtd_probe/mtd_probe.h:24:9: error: unknown type name 'uint32_t'
udev-208-r7:         uint32_t reserved;

Sorry for the trouble :(

Unfortunately I don't think that reverting the CL in master is an option, since it would cause problems in other areas (ARC++, gnubby and potentially others).

As a stopgap you could revert it in a sumo/buddy release branch. We didn't encounter the build error when udev-208 was still in use, I suppose we see it now due to a compiler update. Please apply CL:510844 to fix it. A few days ago udev-208 has been removed from master, if you want to experiment with it you'll have to revert CL:505711.

I don't have a good understanding how virtual keyboards interact with the system, if someone has a pointer that could be helpful. I suspect that Chrome is not receiving a uevent it expects or that the order of the events might be different.

Does the keyboard pop up when running 'udevadm trigger'?

It could also help to run 'udevadm monitor -u -p -s input' and collect its output and execute 'udevadm trigger -s input' in another terminal, for both udev-208 and udev-225.

In order to debug myself: does someone have a device I could borrow or is there a hack to simulate kiosk mode on a Chromebook with touchscreen?

I just had a chat with dtor@ who worked on a CL touching the virtual keyboard on Sumo. His CL:321121 should fix the problem.

Keigo, what buttons does buddy unit have on it? Brightness? Volume? Or power only?

I'll prepare the fix for buddy once I know what keys to add to the keymap in overlay-buddy/chromeos-base/chromeos-bsp-buddy/files/61-buddy-keyboard.hwdb

Looks like it's power only.

Keigo, could you please give https://chromium-review.googlesource.com/#/c/513029/ a spin as I do not have a buddy. 

Thank you! I will check it on my device soon.

Unfortunately the CL didn't fix the issue.
I patched 513029 on ToT and create buddy image. Virtual keyboard doesn't show up with the image.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/740126c36a079bc65cbbd0af82d4955cb2d40296

commit 740126c36a079bc65cbbd0af82d4955cb2d40296
Author: Dmitry Torokhov <dtor@chromium.org>
Date: Thu May 25 09:33:07 2017

Ninja: adjust to new udev syntax

The new udev version changed syntax for dmi-based keyboard quirks, let's
adjust to the new syntax.

BUG= chromium:711069 
TEST=Boot on ninja, verify we are waiting on "searching for
mouse/keyboard" screen until we connect either keyboard or a mouse.

Change-Id: Ifbd1c9b65a81267692dbc5081b5009d0a12230c9
Signed-off-by: Dmitry Torokhov <dtor@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/513399
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[rename] https://crrev.com/740126c36a079bc65cbbd0af82d4955cb2d40296/overlay-ninja/chromeos-base/chromeos-bsp-ninja/chromeos-bsp-ninja-0.0.1-r11.ebuild
[modify] https://crrev.com/740126c36a079bc65cbbd0af82d4955cb2d40296/overlay-ninja/chromeos-base/chromeos-bsp-ninja/files/61-ninja-keyboard.hwdb

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/b38f7a578e8390a7575be3373332d5615fd8fe0e

commit b38f7a578e8390a7575be3373332d5615fd8fe0e
Author: Dmitry Torokhov <dtor@chromium.org>
Date: Fri May 26 00:15:54 2017

Buddy: adjust to new udev syntax

The new udev version changed syntax for dmi-based keyboard quirks, let's
adjust to the new syntax.

BUG= chromium:711069 
TEST=Boot on buddy, verify virtual keyboard is shown when touching
input field when physical keyboard is not connected.

Change-Id: I85bd7088057b65a317b34d54c9e97af1300a3711
Signed-off-by: Dmitry Torokhov <dtor@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/513029
Reviewed-by: Benson Leung <bleung@chromium.org>

[rename] https://crrev.com/b38f7a578e8390a7575be3373332d5615fd8fe0e/overlay-buddy/chromeos-base/chromeos-bsp-buddy/chromeos-bsp-buddy-0.0.1-r15.ebuild
[modify] https://crrev.com/b38f7a578e8390a7575be3373332d5615fd8fe0e/overlay-buddy/chromeos-base/chromeos-bsp-buddy/files/61-buddy-keyboard.hwdb

OK. I confirmed VK appears on ToT. Thank you very much!
Could you cherry-pick the patches to M58 and M59?

Given this is marked as P0 requesting merge to both 59 and 58. The changes are limited to adjusting keymap files for given boards only (they live on boards overlay) and will not affect any other devices.

Consider this merge approved for 58 if it makes it into 59, however note that 58 is a dead branch and has no more releases planned.

This bug requires manual review: We are only 10 days from stable.
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), gkihumba@(ChromeOS), Abdul Syed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/201ef5ca989d0c51ce4047ed2da006a28426e035

commit 201ef5ca989d0c51ce4047ed2da006a28426e035
Author: Dmitry Torokhov <dtor@chromium.org>
Date: Wed May 31 17:09:50 2017

Buddy: adjust to new udev syntax

The new udev version changed syntax for dmi-based keyboard quirks, let's
adjust to the new syntax.

BUG= chromium:711069 
TEST=Boot on buddy, verify virtual keyboard is shown when touching
input field when physical keyboard is not connected.

Change-Id: I85bd7088057b65a317b34d54c9e97af1300a3711
Signed-off-by: Dmitry Torokhov <dtor@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/513029
Reviewed-by: Benson Leung <bleung@chromium.org>
(cherry picked from commit b38f7a578e8390a7575be3373332d5615fd8fe0e)
Reviewed-on: https://chromium-review.googlesource.com/519607
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[rename] https://crrev.com/201ef5ca989d0c51ce4047ed2da006a28426e035/overlay-buddy/chromeos-base/chromeos-bsp-buddy/chromeos-bsp-buddy-0.0.1-r15.ebuild
[modify] https://crrev.com/201ef5ca989d0c51ce4047ed2da006a28426e035/overlay-buddy/chromeos-base/chromeos-bsp-buddy/files/61-buddy-keyboard.hwdb

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/0ca05b716ed5af62b60e9d3429184ab2ea2d57a0

commit 0ca05b716ed5af62b60e9d3429184ab2ea2d57a0
Author: Dmitry Torokhov <dtor@chromium.org>
Date: Wed May 31 17:27:36 2017

Ninja: adjust to new udev syntax

The new udev version changed syntax for dmi-based keyboard quirks, let's
adjust to the new syntax.

BUG= chromium:711069 
TEST=Boot on ninja, verify we are waiting on "searching for
mouse/keyboard" screen until we connect either keyboard or a mouse.

Change-Id: Ifbd1c9b65a81267692dbc5081b5009d0a12230c9
Signed-off-by: Dmitry Torokhov <dtor@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/513399
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
(cherry picked from commit 740126c36a079bc65cbbd0af82d4955cb2d40296)
Reviewed-on: https://chromium-review.googlesource.com/519608

[rename] https://crrev.com/0ca05b716ed5af62b60e9d3429184ab2ea2d57a0/overlay-ninja/chromeos-base/chromeos-bsp-ninja/chromeos-bsp-ninja-0.0.1-r11.ebuild
[modify] https://crrev.com/0ca05b716ed5af62b60e9d3429184ab2ea2d57a0/overlay-ninja/chromeos-base/chromeos-bsp-ninja/files/61-ninja-keyboard.hwdb

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/9d1ecbc7f34d7658727cd6c04106dd58b8d8fa1a

commit 9d1ecbc7f34d7658727cd6c04106dd58b8d8fa1a
Author: Dmitry Torokhov <dtor@chromium.org>
Date: Wed May 31 18:43:11 2017

Buddy: adjust to new udev syntax

The new udev version changed syntax for dmi-based keyboard quirks, let's
adjust to the new syntax.

BUG= chromium:711069 
TEST=Boot on buddy, verify virtual keyboard is shown when touching
input field when physical keyboard is not connected.

Change-Id: I85bd7088057b65a317b34d54c9e97af1300a3711
Signed-off-by: Dmitry Torokhov <dtor@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/513029
Reviewed-by: Benson Leung <bleung@chromium.org>
(cherry picked from commit b38f7a578e8390a7575be3373332d5615fd8fe0e)
Reviewed-on: https://chromium-review.googlesource.com/519609
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/9d1ecbc7f34d7658727cd6c04106dd58b8d8fa1a/overlay-buddy/chromeos-base/chromeos-bsp-buddy/files/61-buddy-keyboard.hwdb
[rename] https://crrev.com/9d1ecbc7f34d7658727cd6c04106dd58b8d8fa1a/overlay-buddy/chromeos-base/chromeos-bsp-buddy/chromeos-bsp-buddy-0.0.1-r14.ebuild

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/f3a61b64abc1f8e69a4ed6bde5eb8b40de5d01fe

commit f3a61b64abc1f8e69a4ed6bde5eb8b40de5d01fe
Author: Dmitry Torokhov <dtor@chromium.org>
Date: Wed May 31 18:50:25 2017

Ninja: adjust to new udev syntax

The new udev version changed syntax for dmi-based keyboard quirks, let's
adjust to the new syntax.

BUG= chromium:711069 
TEST=Boot on ninja, verify we are waiting on "searching for
mouse/keyboard" screen until we connect either keyboard or a mouse.

Change-Id: Ifbd1c9b65a81267692dbc5081b5009d0a12230c9
Signed-off-by: Dmitry Torokhov <dtor@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/513399
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
(cherry picked from commit 740126c36a079bc65cbbd0af82d4955cb2d40296)
Reviewed-on: https://chromium-review.googlesource.com/519610

[rename] https://crrev.com/f3a61b64abc1f8e69a4ed6bde5eb8b40de5d01fe/overlay-ninja/chromeos-base/chromeos-bsp-ninja/chromeos-bsp-ninja-0.0.1-r11.ebuild
[modify] https://crrev.com/f3a61b64abc1f8e69a4ed6bde5eb8b40de5d01fe/overlay-ninja/chromeos-base/chromeos-bsp-ninja/files/61-ninja-keyboard.hwdb

Hi Bernie, dev team
got error 404 when opening last and most of commit pages:
https://chromium.googlesource.com/chromium/src/+/f3a61b64abc1f8e69a4ed6bde5eb8b40de5d01fe

Also When I am trying to find an image using any commit, still cannot find any image, can you please advise correct image version which includes it (e.g. for buddy)?

Let's not reopen bugs just because you can't find the commit because you are looking in chrome source whereas the change is in board-overlays repo:

"The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/f3a61b64abc1f8e69a4ed6bde5eb8b40de5d01fe"

The CL to fix buddy in 59 is this one: https://chromium-review.googlesource.com/#/c/519607/ and if you look at it it says "Landed in	9460.58.0". So grab any 59 image after 9460.58.0 and you should have the fix.