Google Chrome Update Question

[Tim Evans]

Usually, dnf updates take care of updating Google Chrome.  Lately, for 
the past week or so, however, there's a big pink button in Chrome's 
status bar labeled "Update," but dnf insists I have the latest version 
(google-chrome-stable-115.0.5790.110-1.x86_64).

If you click this button, it tells you it's unable to update Chrome and 
asks if you want to re-install.

Is this just a new idiot light that means nothing, or is there some sort 
of conflict with update versions?

Thanks.

[Chris Adams]

Once upon a time, Tim Evans <tkevans(a)tkevans.com&gt; said:
>  Usually, dnf updates take care of updating Google Chrome.  Lately,
>  for the past week or so, however, there's a big pink button in
>  Chrome's status bar labeled "Update," but dnf insists I have the
>  latest version (google-chrome-stable-115.0.5790.110-1.x86_64). 
Looks like you have some issue with the Google Chrome repo - the latest
version is in fact google-chrome-stable-117.0.5938.149-1.x86_64.

Does "dnf --refresh list updates" show any errors when fetching the repo
data?
-- 
Chris Adams <linux(a)cmadams.net&gt;

[Tim Evans]

On 10/10/23 19:11, Chris Adams wrote:
>  Once upon a time, Tim Evans <tkevans(a)tkevans.com&gt; said:
> > Usually, dnf updates take care of updating Google Chrome.  Lately,
> > for the past week or so, however, there's a big pink button in
> > Chrome's status bar labeled "Update," but dnf insists I have the
> > latest version (google-chrome-stable-115.0.5790.110-1.x86_64).
>  
>  Looks like you have some issue with the Google Chrome repo - the latest
>  version is in fact google-chrome-stable-117.0.5938.149-1.x86_64.
>  
>  Does "dnf --refresh list updates" show any errors when fetching the repo
>  data? 
Returns nothing.  And...

# dnf list all | grep -i google-chrome
google-chrome-stable.x86_64 
                 115.0.5790.110-1

[Mike Wright]

On 10/10/23 15:38, Tim Evans wrote:
>  Usually, dnf updates take care of updating Google Chrome.  Lately,
> for 
>  the past week or so, however, there's a big pink button in Chrome's 
>  status bar labeled "Update," but dnf insists I have the latest version 
>  (google-chrome-stable-115.0.5790.110-1.x86_64).
>  
>  If you click this button, it tells you it's unable to update Chrome and 
>  asks if you want to re-install.
>  
>  Is this just a new idiot light that means nothing, or is there some sort 
>  of conflict with update versions?
>   
I'd put it in the idiot light category.  It is almost always on for me 
but when I follow the instructions  Settings->About??? there is no 
Update button which means I don't need to update.  Useless and annoying.

Last time I got that I downloaded the latest package and installed it 
over the top and the warning has disappeared, at least for the time being.

[Tom Horsley]

Don't know if it is relevant, but a few weeks ago google chrome
utterly refused to update due to some mysterious error it printed
meaningless gibberish about.

I uninstalled it completely, and downloaded new rpm from scratch from the
google download site. I installed it again, and it has been fine ever since then.

[Tim Evans]

On 10/10/23 18:38, Tim Evans wrote:
>  Usually, dnf updates take care of updating Google Chrome.  Lately,
> for 
>  the past week or so, however, there's a big pink button in Chrome's 
>  status bar labeled "Update," but dnf insists I have the latest version 
>  (google-chrome-stable-115.0.5790.110-1.x86_64).
>  
>  If you click this button, it tells you it's unable to update Chrome and 
>  asks if you want to re-install.
>  
>  Is this just a new idiot light that means nothing, or is there some sort 
>  of conflict with update versions? 
OK, for whatever unknown reason, /etc/yum.repos.d/google-chrome.repo had 
the 'enabled' flag set to 0.  Setting it to 1 allowed dnf to update 
Chrome to version 118.0.5993.70--and the pink button is gone.

I see the same thing on another similarly behaving system, with the mod 
date on the file as July 26. There is an 'rpmnew' version of that file 
(dated 2/3/2022) with the same flag set to 0, but with another line that 
says "skip_if_unavailable=True" This line is not present in the 
currently used file.

[Neal Becker]

On Tue, Oct 10, 2023 at 7:46 PM Tim Evans <tkevans(a)tkevans.com&gt; wrote:

>  On 10/10/23 18:38, Tim Evans wrote:
>  > Usually, dnf updates take care of updating Google Chrome.  Lately, for
>  > the past week or so, however, there's a big pink button in Chrome's
>  > status bar labeled "Update," but dnf insists I have the latest version
>  > (google-chrome-stable-115.0.5790.110-1.x86_64).
>  >
>  > If you click this button, it tells you it's unable to update Chrome and
>  > asks if you want to re-install.
>  >
>  > Is this just a new idiot light that means nothing, or is there some sort
>  > of conflict with update versions?
>
>  OK, for whatever unknown reason, /etc/yum.repos.d/google-chrome.repo had
>  the 'enabled' flag set to 0.  Setting it to 1 allowed dnf to update
>  Chrome to version 118.0.5993.70--and the pink button is gone.
>
>  I see the same thing on another similarly behaving system, with the mod
>  date on the file as July 26. There is an 'rpmnew' version of that file
>  (dated 2/3/2022) with the same flag set to 0, but with another line that
>  says "skip_if_unavailable=True" This line is not present in the
>  currently used file.
>  
Also, don't forget that you have to restart chrome after updating or you'll
continue to see the notification.

[Stephen Morris]

On 11/10/23 21:59, Neal Becker wrote:
>  On Tue, Oct 10, 2023 at 7:46 PM Tim Evans <tkevans(a)tkevans.com&gt; wrote:
>
>      On 10/10/23 18:38, Tim Evans wrote:
>      > Usually, dnf updates take care of updating Google Chrome. 
>      Lately, for
>      > the past week or so, however, there's a big pink button in Chrome's
>      > status bar labeled "Update," but dnf insists I have the latest
>      version
>      > (google-chrome-stable-115.0.5790.110-1.x86_64).
>      >
>      > If you click this button, it tells you it's unable to update
>      Chrome and
>      > asks if you want to re-install.
>      >
>      > Is this just a new idiot light that means nothing, or is there
>      some sort
>      > of conflict with update versions?
>
>      OK, for whatever unknown reason,
>      /etc/yum.repos.d/google-chrome.repo had
>      the 'enabled' flag set to 0.  Setting it to 1 allowed dnf to update
>      Chrome to version 118.0.5993.70--and the pink button is gone.
>
>      I see the same thing on another similarly behaving system, with
>      the mod
>      date on the file as July 26. There is an 'rpmnew' version of that
>      file
>      (dated 2/3/2022) with the same flag set to 0, but with another
>      line that
>      says "skip_if_unavailable=True" This line is not present in the
>      currently used file.
>
>
>  Also, don't forget that you have to restart chrome after updating or 
>  you'll continue to see the notification.
>  
There is this bug https://bugzilla.redhat.com/show_bug.cgi?id=2170839 
documenting a defect with the google-chrome F38 repositories, but the 
last entry in the bug specifies that the issue has been fixed, so the 
update issues reported here may have just been a temporary glitch.

regards,
Steve

>  _______________________________________________
>  users mailing list --users(a)lists.fedoraproject.org
>  To unsubscribe send an email tousers-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List
> Archives:https://lists.fedoraproject.org/archives/list/[e-mail]...
>  Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue
>

[Tim Evans]

On 10/21/23 20:12, Stephen Morris wrote:
>  On 11/10/23 21:59, Neal Becker wrote:
> >
> >
> > On Tue, Oct 10, 2023 at 7:46 PM Tim Evans <tkevans(a)tkevans.com&gt; wrote:
> >
> >     On 10/10/23 18:38, Tim Evans wrote:
> >     > Usually, dnf updates take care of updating Google Chrome. 
> >     Lately, for
> >     > the past week or so, however, there's a big pink button in Chrome's
> >     > status bar labeled "Update," but dnf insists I have the latest
> >     version
> >     > (google-chrome-stable-115.0.5790.110-1.x86_64).
> >     >
> >     > If you click this button, it tells you it's unable to update
> >     Chrome and
> >     > asks if you want to re-install.
> >     >
> >     > Is this just a new idiot light that means nothing, or is there
> >     some sort
> >     > of conflict with update versions?
> >
> >     OK, for whatever unknown reason,
> >     /etc/yum.repos.d/google-chrome.repo had
> >     the 'enabled' flag set to 0.  Setting it to 1 allowed dnf to update
> >     Chrome to version 118.0.5993.70--and the pink button is gone.
> >
> >     I see the same thing on another similarly behaving system, with
> >     the mod
> >     date on the file as July 26. There is an 'rpmnew' version of that
> >     file
> >     (dated 2/3/2022) with the same flag set to 0, but with another
> >     line that
> >     says "skip_if_unavailable=True" This line is not present in the
> >     currently used file.
> >
> >
> > Also, don't forget that you have to restart chrome after updating or 
> > you'll continue to see the notification.
>  There is this bug https://bugzilla.redhat.com/show_bug.cgi?id=2170839 
>  documenting a defect with the google-chrome F38 repositories, but the 
>  last entry in the bug specifies that the issue has been fixed, so the 
>  update issues reported here may have just been a temporary glitch. 
Thanks.  After posting my last reply, this dawned on me:  If the 
chrome-specific repo was disabled (as I had discovered), and I was only 
a couple of releases behind, then I must've been getting recent releases 
via the main Fedora repo(s) up until shortly before my original post.

Regards.

[Stephen Morris]

On 23/10/23 02:25, Tim Evans wrote:
>  On 10/21/23 20:12, Stephen Morris wrote:
> > On 11/10/23 21:59, Neal Becker wrote:
> >>
> >>
> >> On Tue, Oct 10, 2023 at 7:46 PM Tim Evans <tkevans(a)tkevans.com&gt; wrote:
> >>
> >>     On 10/10/23 18:38, Tim Evans wrote:
> >>     > Usually, dnf updates take care of updating Google Chrome.     
> >> Lately, for
> >>     > the past week or so, however, there's a big pink button in 
> >> Chrome's
> >>     > status bar labeled "Update," but dnf insists I have the
> latest
> >>     version
> >>     > (google-chrome-stable-115.0.5790.110-1.x86_64).
> >>     >
> >>     > If you click this button, it tells you it's unable to update
> >>     Chrome and
> >>     > asks if you want to re-install.
> >>     >
> >>     > Is this just a new idiot light that means nothing, or is there
> >>     some sort
> >>     > of conflict with update versions?
> >>
> >>     OK, for whatever unknown reason,
> >>     /etc/yum.repos.d/google-chrome.repo had
> >>     the 'enabled' flag set to 0.  Setting it to 1 allowed dnf to update
> >>     Chrome to version 118.0.5993.70--and the pink button is gone.
> >>
> >>     I see the same thing on another similarly behaving system, with
> >>     the mod
> >>     date on the file as July 26. There is an 'rpmnew' version of that
> >>     file
> >>     (dated 2/3/2022) with the same flag set to 0, but with another
> >>     line that
> >>     says "skip_if_unavailable=True" This line is not present in the
> >>     currently used file.
> >>
> >>
> >> Also, don't forget that you have to restart chrome after updating or 
> >> you'll continue to see the notification.
> > There is this bug https://bugzilla.redhat.com/show_bug.cgi?id=2170839 
> > documenting a defect with the google-chrome F38 repositories, but the 
> > last entry in the bug specifies that the issue has been fixed, so the 
> > update issues reported here may have just been a temporary glitch.
>
>  Thanks.  After posting my last reply, this dawned on me:  If the 
>  chrome-specific repo was disabled (as I had discovered), and I was 
>  only a couple of releases behind, then I must've been getting recent 
>  releases via the main Fedora repo(s) up until shortly before my 
>  original post.
>  
Sorry for the late response, I wasn't aware that google-chrome was in 
the fedora repositories, as the only way I've been able to get chrome 
was to installed the chrome specific repo. From the bug track above, 
there is an indication that the repo was disabled at a particular point 
in time, so you may have been getting updates from the chrome repo until 
the disabling happened.

regards,
Steve

>  Regards.
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: 
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: 
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam, report it: 
>  https://pagure.io/fedora-infrastructure/new_issue
>

[Jonathan Billings]

On Nov 1, 2023, at 18:25, Stephen Morris <samorris(a)netspace.net.au&gt; wrote:
>  Sorry for the late response, I wasn't aware that google-chrome
> was in the fedora repositories, as the only way I've been able to get chrome was to
> installed the chrome specific repo. From the bug track above, there is an indication that
> the repo was disabled at a particular point in time, so you may have been getting updates
> from the chrome repo until the disabling happened. 
Google’s ‘google-chrome-stable’ package isn’t in Fedora’s repositories, however, it is one
of the third party repos that Fedora can enable after the system is set up. 

The bug mentioned above is about package signatures, and how Google’s RPM in its repo was
causing issues due to a change in the security policy. 

Most likely, you are still getting your google-chrome package from Google and their
repository, so if it was disabled, that needs to be fixed. 

-- 
Jonathan Billings