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

Issue 597242 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression



Sign in to add a comment

[Regression]: Unwanted "Getting Started" page is seen on creating a New person/ Opening Incognito mode for first time

Project Member Reported by sc00335...@techmahindra.com, Mar 23 2016

Issue description

Version: 50.0.2661.49 beta
OS: Ubuntu 12.04,14.04

What steps will reproduce the problem?
(1) Fresh launch chrome >> By default one person is seen[You will get 2 tabs- Chrome sign in page and Getting started page]
(2) Now Add a Person[Person 2] or hit "ctrl+shift+n" for Incognito Window and observe

Expected: No Getting Started page should be seen on creating new person or opening incognito person for first time

Actual: Instead Unwanted getting started page is seen on adding New person or opening incognito for first time.

NOTE: This "Getting started" page is seen only for first creation of user. From second user it is not seen.

This is a regression issue broken in M50. Issue is not seen in windows.

good build:50.0.2658.0  dev (64-bit)
bad build:50.0.2659.0  dev (64-bit)

Chromium is invoking all good builds and got changelog as

CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/5477c3e6bf9fbe689f23afc431646c4007c61a25..1152e786b74c1bbba74af386eb9757f3f8713add

Hence re-bisected again by changing good and bad builds. Even now all chromium builds are good and changelog is

https://chromium.googlesource.com/chromium/src/+log/041151c642ee1ce37e41cd6365b2f2fa456bb4bc..4acd739260230f59c08858a31e795c2dcfdc54d4

Suspecting  https://codereview.chromium.org/1645313002 from cahngelog

@fs: Please help in re-assigning if it is not related to your change.


 
Attaching videos for reference.
Actual_gettingstartedpage.ogv
1.1 MB Download
Expected_gettingstartedpage.ogv
1.6 MB Download

Comment 2 by f...@opera.com, Mar 23 2016

Components: UI>Browser>FirstRun
My CL affects what gets loaded (and not) in <object>s, so it seems unlikely to have anything to do with this regression.

I've tried to bisect this myself and haven't been able to even reproduce the problem once. Based on what is written above ("all good builds", "all chromium builds are good") it doesn't seem that you managed to reproduce it - at least not during bisect. My WM differs from the one on the video, so I can't be sure it's not related to the exact method used to "Add Person".

Without any real data to go on it's difficult to reassign this to someone proper, so I'll put it under the FirstRun component and hope someone sees it. If not, we'll have to randomly reassign in a day or two.

Comment 3 by f...@opera.com, Mar 29 2016

Cc: gab@chromium.org cpu@chromium.org grt@chromium.org
Randomly CCing people from chrome/browser/first_run/OWNERS in the hope that they can help triage/reassign/funnel this.

Comment 4 by f...@opera.com, Apr 4 2016

Cc: f...@opera.com
Owner: ----
Status: Available (was: Assigned)

Comment 5 by gab@chromium.org, Apr 7 2016

Status: WontFix (was: Available)
Can't repro and from discussion above it seems no one can either? Closing until an actual repro is presented.

Sign in to add a comment