New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 614549 link

Starred by 5 users
Status: Untriaged
Owner: ----
Cc:
█ sdavern@chromium.org
aghuie@chromium.org
█ sduraisamy@chromium.org
█ pkakasi@chromium.org
tdres...@chromium.org
█ vidster@chromium.org
█ gbirtchnell@chromium.org
spang@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

[Bug] Aopen Chromebase touchscreen fails after update to M50 - Kiosk

Project Member Reported by johnsonrichard@chromium.org, May 24 2016 
Version of Google Chrome (Wrench-> About Google Chrome):

Version:50.0.2661.103 (64bit)
Platform 7978.74.0
Firmware Google_sumo 5216.382.5

Version of MSI (if applicable):
Using group policy settings? Yes/No

Aopen Chromebase device was updated from M49 to M50. Touchscreen failed to respond to touch. This has been replicated across 2 devices now. No customer reports as of yet.

Wiping and re enrolling does not solve issue. 

Unable to use device for Demo purposes.

Comment 1 by atwilson@chromium.org, May 31 2016

Cc: sduraisamy@chromium.org
Components: -Enterprise Internals>Input>Touch>Screen
If we can reproduce this in-house, someone on the input team should probably take a look.

Comment 2 by atwilson@chromium.org, May 31 2016

Labels: -Type-Bug -Pri-2 Pri-1 Type-Bug-Regression

Comment 3 by kathrelk...@chromium.org, May 31 2016

Cc: tdres...@chromium.org spang@chromium.org
Status: Untriaged (was: Unconfirmed)

Comment 4 by aghuie@chromium.org, May 31 2016 

Tested on a chromebase in developer mode on 50.0.2661.10 with no issues. Device with signed in user has no problems with touchscreen (both mouse and keyboard).

Specific devices in question may have a unique configuration or policies in place.
►

Sign in to add a comment