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

Issue 806590 link

Starred by 7 users

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression

Blocked on:
issue 805443



Sign in to add a comment

Browser keeps asking for a restart in order to "update"

Reported by regis.ca...@gmail.com, Jan 28 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.18 Safari/537.36

Steps to reproduce the problem:
1. Just launch the browser and wait

What is the expected behavior?
No green⋮asking for a restart

What went wrong?
The⋮turns green after some time and calls for a browser restart.
After a restart the version is still 65.0.3325.18

Did this work before? Yes previous dev version was fine

Chrome version: 65.0.3325.18  Channel: dev
OS Version: Ubuntu 17.10 / gnome shell
Flash Version: 

This bug might not be browser related, maybe the update "channel" sends wrong data.
 
Labels: Needs-Bisect Needs-Triage-M65
Got another "green" today, if you guys need more info (debug log maybe), feel free to ask.

Regards
Capture d’écran de 2018-01-28 22-05-45.png
1.8 KB View Download
Cc: vamshi.k...@techmahindra.com
Labels: Triaged-ET Needs-Feedback
Thanks for filing the issue!

Unable to reproduce the issue on reported chrome version 65.0.3325.18 and on the latest stable 64.0.3282.119 using ubuntu 14.04 with the below mentioned steps.
1. Launched Chrome 
2. Observed that no green ⋮ is seen.

@Reporter: Could you please let us know if the same issue is seen on other machines/OS platforms(if possible). Any further inputs from your end may help us to triage the issue in a better way.  
@vamshi

I didn't see any "green ⋮" since my comment with the screenshot, before that I got it at least 4 times. I did look at my apt logs and there's was no update (last one is 26/01/2018) 

I can not say about other OS / machine, this is the only machine I use with the dev version (I didn't notice this issue with beta under OSX).

As a side note, I saw that during the week-end, so the browser/machine did stay "up" all day long.
Project Member

Comment 5 by sheriffbot@chromium.org, Jan 29 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
@Reporter: It is understood from your comment#4 that the issue is no longer seen from your end, Please confirm if we can close this.

Thanks!

Comment 7 Deleted

Project Member

Comment 8 by sheriffbot@chromium.org, Jan 30 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 9 Deleted

I got one "please restart", just now. So this is still an issue for me.
Enclosed is a before and after the restart of the "about" page.
Capture d’écran de 2018-01-30 21-25-33.png
37.7 KB View Download
Capture d’écran de 2018-01-30 21-27-58.png
42.7 KB View Download
Labels: -Needs-Bisect OS-Mac OS-Windows
Unable to reproduce the issue on reported chrome version 65.0.3325.18 and latest dev 66.0.3335.0 using Ubuntu 14.04 with the below mentioned steps.
1. Launched Chrome 
2. Observed that no green ⋮ is seen.
Attaching the screen shot for reference.

As the issue is not reproducible from ET end, requesting someone from UI team to have a look into this and help in further triaging the issue. Hence removing Needs-Bisect label.

Thanks!
Labels: -OS-Windows -OS-Mac
806590
111 KB View Download
Labels: TE-NeedsTriageHelp
As the issue is not reproducible from TE-end as per comment #3, #4 and #11. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!
Just so you guys know, I got another "green" with 65.0.3325.31 around 9pm (Paris time)

Regards,

Comment 16 by ajha@chromium.org, Feb 7 2018

Components: -UI Internals>Installer

Comment 17 by neis@chromium.org, Feb 8 2018

Cc: neis@chromium.org
I'm having the same issue, running the dev version (google-chrome-unstable on glinux). Asked me to restart about 7 times in a single week.

Comment 18 by neis@chromium.org, Feb 8 2018

Labels: -Pri-2 Pri-1

Comment 19 by neis@chromium.org, Feb 8 2018

I had also filed a report via Chrome's "Report an issue" using my email address neis@google.com. But no idea where that ended up, I can't find it.

Comment 20 by ajha@chromium.org, Feb 8 2018

Cc: rbasuvula@chromium.org
Labels: -TE-NeedsTriageHelp TE-NeedsTriageFromHYD
Cc'ing Raj@ from installer team to check this in Inhouse environment.
I also am having this happen consistently. As long as I have chrome running for at least an hour or two, even if it's in the background with all tabs closed, the green dots and the reload to update option will show up. I am running chrome dev 65.0.3325.51 on Ubuntu 16.04. 

Comment 22 by neis@chromium.org, Feb 12 2018

Status: Untriaged (was: Unconfirmed)
Cc: pbomm...@chromium.org
Labels: -TE-NeedsTriageFromHYD RegressedIn-65 M-65 Target-65 FoundIn-65
Tested on chrome #65.0.3325.18 and 65.0.3325.51 on Ubuntu 17.10 and able to reproduce the issue.Please find the screen shots for your reference.

Steps Followed:
---------------
1.Install chrome #65.0.3325.18/51 and wait for more than 5-6hrs.
2.Update icon is displaying.
3.Update the chrome version and relaunch able to see the same version.

Note:
1.Not able to reproduce the issue on latest dev build# 66.0.3346.8 & Canary #66.0.3350.0
2.Able to reproduce in M65 branch builds only
3.Unable to provide the bisect results as issue not reproduce with in shot time.

So providing manual CL from omahaproxy but unable find the possible suspect from below change log:

https://chromium.googlesource.com/chromium/src/+log/65.0.3325.0..65.0.3325.18?pretty=fuller&n=10000

Could some one from Installers dev team please take a look in to this issue.

Thank You!

806590.png
454 KB View Download
Cc: nyerramilli@chromium.org
 Issue 809394  has been merged into this issue.
Cc: thomasanderson@chromium.org
Owner: thomasanderson@chromium.org
Status: Assigned (was: Untriaged)
Also experiencing this issue in Arch Linux on the dev channel.  Since this issue takes several hours to repro, I'm going to add some logging (dev channel only) for when the icon updates.
Cc: gab@chromium.org
Status: Fixed (was: Assigned)
I think this is fixed now.  Here's what I believe happened: 

"chrome --version" broke ( bug 805443 ) and would produce no output.  Our upgrade detector runs "/proc/self/cmdline --version" every 2 hours to check if the installed version of Chrome is newer than the running version (https://cs.chromium.org/chromium/src/chrome/browser/upgrade_detector_impl.cc?rcl=2fefc4bd0b63b9be05846fddaaf47047f103544c&l=126).  If the output is empty, we would conservatively suggest an upgrade.

Comment 28 by gab@chromium.org, Feb 24 2018

Blockedon: 805443
Thanks, attaching to other bug for the record for next time we try this.

Sign in to add a comment