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

Issue 811282 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

dev mode transition UI: new fast wipe looks diff from old slow wipe

Reported by jenny...@intel.corp-partner.google.com, Feb 12 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36
Platform: Multiple platforms

Steps to reproduce the problem:
What steps will reproduce the problem?
1. Create an USB stick with recovery OS image.
2. Boot the DUT in Normal mode (non dev mode) by setting GBB – 0x0.
/us/share/vboot/bin/set_gbb_flags 0
3. Go to recovery mode by pressing “vol up + vol down + power button” keys for 9secs.
4. Insert recovery USB stick.
5. Verify these screens (with messages) are correctly displayed, during "Verification", "Recovery" & "Completion" stages. 
a.) Verification (integrity check) progress screen: 
(ChromeOS Logo) 
"You are about to recover your computer. Please make sure it is plugged in to a power source."
"If you want to cancel recovery, press the power button and hold it down until the computer turns off (this takes upto 8 seconds). It is safe to do this at any time during verification."
"Verifying the integrity of your recovery media..."
(progress bar) 
b.) Recovery progress screen: 
(ChromeOS Logo) 
(Spinner) "System recovery is in progress..."
"This will take a few minutes. Please do not turn off the computer or disconnect the power."
c.) Successful completion screen: 
(ChromeOS Logo) 
(Check Mark) "System recovery is complete."
"Please remove the recovery media and your computer will restart automatically."
6. Remove the USB stick containing valid recovery image.

What is the expected behavior?
What is the expected output?
Recovery OS installation screens messages ("Verification", "Recovery" & "Completion" screens) should display while installing Recovery OS.

What went wrong?
In recovery OS, OS installation progress bar is not seen. In earlier platforms this used to work

Did this work before? N/A 

Chrome version: 65.0.3299.0  Channel: stable
OS Version: 10.0
Flash Version:
 
Non working.jpg
4.8 MB View Download
Working new.jpg
3.1 MB View Download

Comment 1 Deleted

Cc: jwer...@chromium.org
Owner: furquan@chromium.org
Furquan/Julius, who owns this recovery screen?
Owner: rajatja@google.com
This is not a firmware screen. It is put up by the OS. Rajat, do you know who is the right owner for this?

Comment 4 Deleted

Cc: vapier@chromium.org tnagel@chromium.org teravest@chromium.org
The code displaying this progress "bar" is in https://chromium.googlesource.com/chromiumos/platform2/+/master/init/clobber-state. Looks like +Thiemo and +Justin touched it last, so maybe something went wrong in one of those refactor CLs.
edit: In fact, I think this may be working as intended. http://crosreview.com/535846 introduced a mandatory 5 minute delay that uses different UI code than the actual wipe. Looks like that's what you're stuck on in your screenshot (notice the clock in the upper left corner). There's no more actual wipe for modern devices.

Nevertheless, it would probably be better not to have this UI inconsistency. Can we change the forced 5 minute delay to display a similar progress bar through pv?

Comment 7 by vapier@chromium.org, Feb 14 2018

Components: Internals>Installer
Labels: -Restrict-View-Google -Arch-x86_64 -Type-Bug-Regression -Via-Wizard-Other Type-Bug
Summary: dev mode transition UI: new fast wipe looks diff from old slow wipe (was: Soraka: Recovery OS progress bar not displaying while installing Recovery OS)
i think we could implement the same output using pv cheaply:
  pv -etp -L 1 -s 300 /dev/zero >/dev/null
basically reads & writes 1 byte per second for 300 seconds.

i'm going to open this up and adjust the settings since, as Julius noted, the system is working correctly, it's only a diff in the UI.

Comment 8 Deleted

Comment 9 by rajatja@google.com, Feb 14 2018

Owner: vapier@chromium.org
i posted a CL but haven't tested it, and not sure when i will get a chance to:
  https://chromium-review.googlesource.com/919320
Status: Assigned (was: Unconfirmed)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment