Monitor touchscreen no longer works with OS update on Chromebox
Reported by
corysa...@gmail.com,
May 19 2016
|
||||||||
Issue descriptionChrome Version : 50.0.2661.91 (Official Build) (64-bit) URLs (if applicable) : Other browsers tested: Windows 10 What steps will reproduce the problem? Acer T272HL touchscreen has stopped functioning all together on Asus CN60 Chromebox. No indicators of responses to touch. Monitor touchscreen feature worked previously before update and currently works on Win 10.
,
May 27 2016
,
May 31 2016
,
Jun 4 2016
This is set up as a dual screen monitor 1) displayport to Acer T272HL touchscreen and 2) HDMI to Yamaha RXV575 home theatre receiver to Panasonic TC-L42u30 TV. If I unplug the HDMI cable everything works fine, so it has something to do with the HDMI setup with the receiver. It is possible the receiver went through a firmware update that has fouled things up too. I get momentary touch screen functionality (about 1 second worth) when the receiver/tv is booting up when the Chromebox detects a connection and switches to mirroring mode, but then lose it immediately after. So now I am unsure whether it is Chrome OS update, Yamaha receiver update, or receiver/tv setting related, or a combination of above. :( Thanks.
,
Jun 6 2016
+adlr
,
Jun 6 2016
Can we reproduce the issue in mountain view office and bisect it?
,
Jun 7 2016
I'm not crazy. Just got a new out of box Chromebox (looks like Acer CXI2-4GKM) since system shows model 61 Celeron(R) 3205U @ 1.50GHz. Anyways, touch screen worked perfectly with these details: Version 42.0.2311.87 (64-bit) Platform 6812.75.2 (Official Build) stable-channel rikku Firmware Google_Rikku.6301.110.4 it proceed to do an update and became: Version 51.0.2704.79 (64-bit) Platform 8172.47.0 (Official Build) stable-channel rikku Firmware Google_Rikku.6301.110.4 Now, the touch screen doesn't work again, so I don't think it is specific to my Asus CN60 model.
,
Jun 8 2016
adlr@, who is an appropriate owner for this? Folks cc'ed aren't in MTV. Bumping up to Pri-2 - if we find that this is effecting multiple users, we should bump it up to P1.
,
Jun 8 2016
It's hard to diagnose this and find an owner based on the text description here. Can someone repro the issue on a test image and get me, or someone who works on input, to take a look? I want to see if it's the kernel or Chrome that's misbehaving.
,
Jun 8 2016
Sorry, I said P2, and accidentally set this P1. adlr@, who do you think should try to repro this? It sounded like you wanted someone in MTV, such that you'd be able to take a look? Can you assign a reasonable owner?
,
Aug 25 2016
Just wondering whether anybody has an update on this.
,
Aug 25 2016
Over to adlr@ for triage.
,
Sep 30 2016
This may be related. Especially in a dual monitor setup. https://bugs.chromium.org/p/chromium/issues/detail?id=614624
,
Aug 1
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by nyerramilli@chromium.org
, May 19 2016