New issue
Advanced search Search tips

Issue 844347 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Receiving notification about update available despite using the latest version

Reported by orsch...@gmail.com, May 18 2018

Issue description

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

Steps to reproduce the problem:
1. Open Chrome
2. Wait for a little while
3. You should see a yellow exclamation mark

What is the expected behavior?
I expect it to notify me about actual updates available.

What went wrong?
Instead, it tells me an update for Chrome is available. Hence, I went to the Chrome download page and grabbed the latest .rpm and installed it. As you can see from the screenshot attached, it was a false error. I already have the latest version installed. 

So, why does it keep telling me I need to update my Chrome?

Thank you!

Did this work before? N/A 

Chrome version: 66.0.3359.181  Channel: stable
OS Version: Fedora 28
Flash Version:
 
Screenshot from 2018-05-18 10-15-38.png
124 KB View Download

Comment 1 by orsch...@gmail.com, May 19 2018

On a related note, maybe chrome://settings/help could show if there is an update available?

As far as I am aware, it doesn't currently. Correct me if I am wrong. :-)
Labels: Needs-Triage-M66
Components: -UI Internals>Installer
Normally, chrome://settings/help will show you an update is available and prompt you to relaunch.

That said, 66.0.3359.181 is the current Linux stable, so it's odd that it got flagged. Hopefully the installer team can take a look at this.

Comment 5 by orsch...@gmail.com, May 21 2018

Thanks! Looking forward to the insights from the installer team. :-)

Also adding some info about the YUMM repo I have enabled.

/etc/yum.repos.d/google-chrome.repo

[google-chrome]
name=google-chrome
baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
skip_if_unavailable=True
gpgcheck=1
gpgkey=https://dl.google.com/linux/linux_signing_key.pub
enabled=1
enabled_metadata=1
Cc: phanindra.mandapaka@chromium.org
Labels: TE-NeedsTriageFromHYD Triaged-ET
Unable to reproduce the issue on reported version 66.0.3359.181 using Ubuntu 17.10. 

Steps 
--------
1. Launched Chrome
2. Waited for one hour.
3. We are unable to see a yellow exclamation mark

@As we are unable to reproduce the issue from our end. .Let us know if we miss anything. As we don't have ""OS Version: Fedora 28"" to test this issue. Hence forwarding this issue to Inhouse Team to have a look on this issue.

Thanks!
Cc: rbasuvula@chromium.org

Comment 8 by orsch...@gmail.com, May 22 2018

@all currently doing more testing from my side to see if I can reproduce the issue. Haven't seen the exclamation mark for a while now. Not sure why...

Comment 9 by orsch...@gmail.com, May 22 2018

It just happened again. 

Video screencast: https://www.useloom.com/share/0b0a45a62e714861ad6c14afeed86066
Cc: thomasanderson@chromium.org
Tested on Debian Rodete and Fedora and was not able to reproduce the mentioned issue on the reported Chrome #66.0.3359.181.

This issue seems to be similar to the  Issue 806590 .
thomasanderson@ -- Could you please take a look into this issue.

Thanks in advance!
Owner: thomasanderson@chromium.org
Status: WontFix (was: Unconfirmed)
That warning is telling you to restart Chrome, not to update it.  It means you already have the latest version installed from an update, but you're currently running the older version because you haven't restarted yet.

Comment 12 by orsch...@gmail.com, May 23 2018

Hmm I see. So shouldn't the message tell me this then?

Instead of saying update available, I think better to say "restart your Chrome"

:-)
Cc: bettes@chromium.org
+bettes
I seem to recall the message in the menu asking to "restart to update Chrome" at some point.  But now it just says "Update Google Chrome".  Do you know why we changed it?

Sign in to add a comment