Adding screenshots of correct on-screen flow of Welcome app via OOBE from ASUS Chromebook Flip C100PA [board: veyron-minnie].

Final screen "Keep Exploring" button opens Get Help app.  "Finish" button closes Welcome app. Once, tutorial is exited, the only way to repeat it would be through the Get Help app New to Chromebooks section "Take a Tour" button or by powerwashing device to reset to factory settings (https://support.google.com/chromebook/answer/183084).  

Deleted: WelcomeApp-TakeaTourOOBE-1.png 260 KB

	WelcomeApp-TakeaTourOOBE-1.png 260 KB View Download

Deleted: WelcomeApp-TakeaTourOOBE-2.png 87.3 KB

	WelcomeApp-TakeaTourOOBE-2.png 87.3 KB View Download

Deleted: WelcomeApp-TakeaTourOOBE-3.png 160 KB

	WelcomeApp-TakeaTourOOBE-3.png 160 KB View Download

Deleted: WelcomeApp-TakeaTourOOBE-4.png 168 KB

	WelcomeApp-TakeaTourOOBE-4.png 168 KB View Download

Not working on Acer C910 on beta channel.

Just updated my lulu and still experiencing the glitch.

  Version 57.0.2987.32 beta (64-bit)
  Platform 9202.18.2 (Official Build) beta-channel lulu
  ARC Version 3704776
  Firmware Google_Lulu.6301.136.57

However, I've never gotten the window partially off screen, I get the entire window but no 'Next' button in the lower right, see attached.

Deleted: Screenshot 2017-02-15 at 3.04.46 PM.png 2.1 MB

	Screenshot 2017-02-15 at 3.04.46 PM.png 2.1 MB View Download

This is  I get on the C910

Deleted: Screenshot 2017-02-15 at 3.11.58 PM.png 2.1 MB

	Screenshot 2017-02-15 at 3.11.58 PM.png 2.1 MB View Download

RE: #c12

Okay, I *finally* see that my window may be partially off screen, enough to hide the 'Next' button.

Sorry for the confusion.

Initiating tests of Welcome app via "take a tour" buttons present after powerwash OOBE first run and Get Help app "new to chromebooks" topic. 

Still unable to duplicate on any of the three devices listed across various OS versions (incl. M49 initially for older devices). 

Note that errant text sometimes appears in first panel of Welcome app (M57 dev/beta) that has already been addressed and fixed in a separate ticket. 


Today, tested the following on Dell Chromebook 13 7310 — Lulu:  


Google Chrome	57.0.2987.32 (Official Build) beta (64-bit)
Revision	0
Platform	9202.18.2 (Official Build) beta-channel lulu
ARC	3704776

--> text problem remains for initial OOBE panel, can't duplicate off-screen panels  

 
Google Chrome	58.0.3007.0 (Official Build) dev (64-bit)
Revision	0
Platform	9280.0.0 (Official Build) dev-channel lulu
ARC	3725293

--> text fine, panels fine


Google Chrome	56.0.2924.87 (Official Build) (64-bit)
Revision	0
Platform	9000.82.0 (Official Build) stable-channel lulu
ARC	3691121

--> both fine 


Previously, tested Lulu with: 


Google Chrome	49.0.2623.95 (Official Build) (64-bit)
Revision	0
Platform	7834.60.0 (Official Build) stable-channel lulu
[no ARC info] 

--> both fine 


Google Chrome	56.0.2924.87 (Official Build) (64-bit)
Revision	0
Platform	9000.82.0 (Official Build) stable-channel lulu
ARC	3691121

--> both fine 

Today, tested the following on Acer C910 — Yuna:


Google Chrome	57.0.2987.32 (Official Build) beta (64-bit)
Revision	0
Platform	9202.18.0 (Official Build) beta-channel auron_yuna
ARC	3704776

--> text bad, panels fine 


Google Chrome	58.0.3007.0 (Official Build) dev (64-bit)
Revision	0
Platform	9280.0.0 (Official Build) dev-channel auron_yuna
ARC	3725293

--> both fine


Google Chrome	56.0.2924.87 (Official Build) (64-bit)
Revision	0
Platform	9000.82.0 (Official Build) stable-channel auron_yuna
ARC	3691121

--> both fine 


Previously, tested Yuna with: 


Google Chrome	46.0.2490.64 (Official Build) beta (64-bit)
Revision	e93a74bdfa2dff0630d02defd13c5cf6fad9989c
Platform	7390.55.0 (Official Build) beta-channel auron_yuna
[no ARC version] 

--> both fine


Google Chrome	56.0.2924.87 (Official Build) beta (64-bit)
Revision	0
Platform	9000.82.0 (Official Build) beta-channel auron_yuna
ARC	3691121

--> both fine


Google Chrome	54.0.2840.101 (Official Build) (64-bit)
Revision	0
Platform	8743.85.0 (Official Build) stable-channel auron_yuna
[no ARC version listed]

--> GH app-accessed fine (OOBE not tested)


Google Chrome	56.0.2924.87 (Official Build) (64-bit)
Revision	0
Platform	9000.82.0 (Official Build) stable-channel auron_yuna
ARC	3691121

--> text problem, panels fine

Data for mine previously shown at #13 --

Version 57.0.2987.32 beta (64-bit)
Platform 9202.18.0 (Official Build) beta-channel auron_yuna
ARC Version 3704776
Firmware Google_Auron_yuna.6301.59.8

hi Jim.  How are you accessing the Welcome app?  Only through the Get Help app or are you testing via the powerwash OOBE, too?  

I have only used Get Help.

Today, tested the following on Toshiba Chromebook 2 2015 (stable) — Gandof:


Google Chrome	57.0.2987.32 (Official Build) beta (64-bit)
Revision	0
Platform	9202.18.0 (Official Build) beta-channel gandof
ARC	3704776

--> bad text, panels fine 


Google Chrome	58.0.3007.0 (Official Build) dev (64-bit)
Revision	0
Platform	9280.0.0 (Official Build) dev-channel gandof
ARC	3725293

--> no Welcome tour on OOBE, fine on Get Help app access 


Google Chrome	56.0.2924.87 (Official Build) (64-bit)
Revision	0
Platform	9000.82.0 (Official Build) stable-channel gandof
ARC	3691121

--> both fine


Previously, tested Yuna with: 


Google Chrome	55.0.2883.35 (Official Build) beta (64-bit)
Revision	0
Platform	8872.35.0 (Official Build) beta-channel gandof
ARC	3426244

--> both fine 


Google Chrome	56.0.2924.87 (Official Build) beta (64-bit)
Revision	0
Platform	9000.82.0 (Official Build) beta-channel gandof
ARC	3691121

--> both fine


Google Chrome	57.0.2987.32 (Official Build) dev (64-bit)
Revision	0
Platform	9202.18.0 (Official Build) dev-channel gandof
ARC	3704776

--> both fine 

Jim, are you familiar with powerwashing?  It wipes all data from a device, so don't do it unless you have anything needed backed up.  (Your remote google accounts remain as is.)  It returns a device to the Out of Box Experience (OOBE).  

One part of the OOBE historically has been the appearance of the Welcome app. The first step of the app you'll see is a "Howdy, Jim" panel with some other text (see attachment in Comment #1 above).  It'll have a blue button that reads "take a tour."  If you click that, you will run through the rest of the Welcome app, the same three panels that you see after you click "take a tour" in the Get Help app "New to Chromebooks" topic.  The last panel in the Welcome app offers two options: Keep Exploring and Finish.  Finish closes the app, but Keep Exploring will take you to the Get Help app, where you can select New to Chromebooks and then hit the "take a tour" button again.  

To get the OOBE on a device that's already been used, you can click "sign out" then when login reappears, press CTRL+ALT+SHIFT+R, then click restart and follow through with further buttons leading toward Powerwash.  Alternately, you can go to Settings/Advanced Settings/Powerwash and follow through a similar process.  I've noticed that a powerwash doesn't "take" every time and sometimes you have to do it twice to get the actual OOBE with selection of user avatar and Welcome app (although on M58 Dev, I've not seen the Welcome app ever in the OOBE for two devices).  

Since I have not been able to duplicate the error testing the three devices named in the bug across a variety of OS versions (and I've checked a couple of others, too), I'd like to see if powerwashing helps.  Perhaps powerwash, check Welcome App via OOBE and Get Help, switch OS channels, powerwash and repeat.  Try to keep notes as you go, I usually copy/paste the info in Chrome browser at chrome://version as soon as I complete and OOBE test, to keep track of what I just tested.  

Much thanks, for reporting and following through. 

Yes, I am quite familiar with Powerwash. I prefer to keep my device as is and not wipe out the problem. Some of the other TC's have also reported the issue. Perhaps someone else will be willing to do the Powerwash.

The goals behind powerwash recommendation were multiple: to try to isolate the problem beyond any possibly user settings etc that may have happened over time (see if it continues), to perhaps see if that fixes it, and to be able to test the true Welcome app OOBE. 

I'm not sure where to go next if powerwashing is not an option. I've not been able to duplicate on any devices.  I'll think about this more and maybe another idea will come up.

I finally had time available to do the Powerwash.

There was no automatic OOBE intro.

When I went to Help, I was able to successfully do the Tour. The forms displayed properly and the Next buttons worked as expected.

When I Opened Chrome, the new user offers were shown.

Thanks, Jim.  It is a bit of rigmarole to powerwash over and over (took quite some time to hit the lists I included in comments above).  

What device and OS version were you on?  

If it's not M58 dev, then perhaps trying another powerwash might present you with the "Howdy, Jim" OOBE Welcome panel.  Sometimes I found that I had to do it twice (via keyboard and/or settings button) to get a true OOBE to return.  In M58 Dev, it appears the Welcome app as it has traditionally appeared as part of the OOBE has been deprecated. 

Version 57.0.2987.32 beta (64-bit)
Platform 9202.18.0 (Official Build) beta-channel auron_yuna
ARC Version 3704776
Firmware Google_Auron_yuna.6301.59.8

Hi Jim.  So, the Yuna is good with a powerwash.  Might you be interested in trying and reporting on the other two devices listed in this ticket?  

Acer C910 — Yuna
Toshiba Chromebook 2 2015 — Gandof
Dell Chromebook 13 7310 — Lulu 

Btw, looks like if a powerwash is resolving the issue, we are likely going to close this ticket for the time being, unless or until further information can be found to help us get to the root of what's going on here.  

Thanks for all of your time. 

i do not have access to those devices.

Retesting the following after powerwash, I did receive the "Howdy" intro welcome screen, so that is not deprecated as deduced in previous comments. 


Google Chrome	58.0.3007.0 (Official Build) dev (64-bit)
Revision	0
Platform	9280.0.0 (Official Build) dev-channel gandof
ARC	3725293

--> Welcome app works in both OOBE and from Get Help app

Hi, Jim.  Okay, then.  I have tested all three repeatedly, and not been able to duplicate, so we are closing this ticket for now.  

If you do run across this again, please, let us know.  If it does occur again, try to gather as much information about the issue as possible (in addition to OS/channel/device, include any display or other settings that might have been updated during the course of device use that could possibly be relevant).  

Thank you!