New issue
Advanced search Search tips

Issue 856803 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jul 11
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

eve: touchpad firmware update never succeeds

Project Member Reported by tbroch@chromium.org, Jun 26 2018

Issue description

Chrome Version: Dev M69
OS: 10798.0.0
What steps will reproduce the problem?
(1) power on eve

What is the expected result?
Device should boot and successfully update touchpad FW

What happens instead?
touchpad FW update is attempted every boot and fails.

Here's the output from chrome://system touch_fw_version on my Eve PVT that shows failure,

2018-06-26T15:11:08.571879-07:00 NOTICE chromeos-google-touch-firmware-update[1476]: error: Firmware update failed. Current Firmware: rose_v1.1.7102-8fd3ffd8c


Here's a feedback report as well from a user,

https://listnr.corp.google.com/report/85520216202
 
Project Member

Comment 1 by sheriffbot@chromium.org, Jul 2

This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone.

All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly.

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
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 6

This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone.

All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly.

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
Components: Internals>Input>Touch>Pad
Labels: M-69
Status: WontFix (was: Assigned)
No longer seeing this on my device running 10820.0.0.  Guess its fixed by something in here:

https://crosland.corp.google.com/log/10798.0.0..10820.0.0

Sign in to add a comment