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

Issue 757638 link

Starred by 5 users
Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
█ krajshree@chromium.org
ajha@chromium.org
ka...@chromium.org
adlr@chromium.org
sontis@chromium.org
█ sosa@chromium.org
pucchakayala@chromium.org
█ brajkumar@chromium.org
hungte@chromium.org
█ helenzhang@chromium.org
songsuk@chromium.org
█ dbehr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Message missing after the successful recovery, only check mark is displayed (Recovery messages are missing on ToT)

Project Member Reported by pgangishetty@chromium.org, Aug 22 2017 
Chrome Version: 62.0.3190.0
OS: 9864.0.0 (Official build) dev-channel chell
Firmware: Google_Chell.7820.314.0

What steps will reproduce the problem?
(1) Start recovering the board with USB stick
(2) Recovery is successful


What is the expected result?
Message should be displayed about the successful recovery.

What happens instead?
Only check mark is displayed. No message about the successful recovery is displayed.

Please use labels and text to provide additional information.
Screenshot attached.  

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
IMG_5085.JPG
331 KB View Download

Comment 1 by sontis@chromium.org, Aug 22 2017

Cc: sosa@chromium.org adlr@chromium.org
Summary: Message missing after the successful recovery, only check mark is displayed (Recovery messages are missing on ToT) (was: Message missing after the successful recovery, only check mark is displayed)
Able to reproduce this issue on 9864.0.0_auron-paine build.
IMG_3791.JPG
65.1 KB View Download

Comment 2 by sontis@chromium.org, Aug 22 2017

Labels: -Pri-2 ReleaseBlock-Stable Pri-1

Comment 3 by zork@chromium.org, Aug 24 2017

Components: -UI

Comment 4 by son...@google.com, Aug 24 2017 

Still able to reproduce this issue on build 9875.0.0

Comment 5 by rajatja@google.com, Sep 23 2017 

I think this has been fixed now. I saw this issue on Soraka earlier, but do not see it anymore on 9941.0.0 recovery image

Comment 6 by hungte@chromium.org, Oct 6 2017

Cc: hungte@chromium.org pucchakayala@chromium.org songsuk@chromium.org ajha@chromium.org krajshree@chromium.org dbehr@chromium.org brajkumar@chromium.org
 Issue 757370  has been merged into this issue.

Comment 7 by bhthompson@google.com, Oct 13 2017 

If this is fixed on ToT do we have a CL that is suspected of fixing it?

We are planning a stable RC next week and this bug is marked as a blocker.

Comment 8 by bhthompson@google.com, Oct 18 2017

Owner: rajatja@google.com
Any update on this one? We are planning to build a R62 stable RC the evening of the 19th, so we would need to have all fixes merged back to 62 in ~24 hours. 

Are you the right owner Rajat?

Comment 9 by rajatja@google.com, Oct 18 2017

Owner: ----
I think I'm not the right owner, also I do not know if this issue is still seen. I had made a passing obsevation that I saw it on Soraka earlier, but I did not see the issue on 9941.0.0 on Soraka. 

pgangishetty@ idoes this issue still reproduce?

Comment 10 by sontis@chromium.org, Oct 18 2017

Status: WontFix (was: Untriaged)
Not able to reproduce this issue on M62 build 9901.49.0
►

Sign in to add a comment