[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-list
Subject:    Re: Google Chrome Update Question
From:       Neal Becker <ndbecker2 () gmail ! com>
Date:       2023-10-11 10:59:18
Message-ID: CAG3t+pG72ZoA_MfwsCKQ3wpfPX4x4XMK1u934tEK34_K3ZTH+w () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Tue, Oct 10, 2023 at 7:46 PM Tim Evans <tkevans@tkevans.com> 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.

[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Tue, Oct 10, 2023 at 7:46 PM Tim Evans &lt;<a \
href="mailto:tkevans@tkevans.com">tkevans@tkevans.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 10/10/23 18:38, Tim \
Evans wrote:<br> &gt; Usually, dnf updates take care of updating Google Chrome.   \
Lately, for <br> &gt; the past week or so, however, there&#39;s a big pink button in \
Chrome&#39;s <br> &gt; status bar labeled &quot;Update,&quot; but dnf insists I have \
the latest version <br> &gt; (google-chrome-stable-115.0.5790.110-1.x86_64).<br>
&gt; <br>
&gt; If you click this button, it tells you it&#39;s unable to update Chrome and <br>
&gt; asks if you want to re-install.<br>
&gt; <br>
&gt; Is this just a new idiot light that means nothing, or is there some sort <br>
&gt; of conflict with update versions?<br>
<br>
OK, for whatever unknown reason, /etc/yum.repos.d/google-chrome.repo had <br>
the &#39;enabled&#39; flag set to 0.   Setting it to 1 allowed dnf to update <br>
Chrome to version 118.0.5993.70--and the pink button is gone.<br>
<br>
I see the same thing on another similarly behaving system, with the mod <br>
date on the file as July 26. There is an &#39;rpmnew&#39; version of that file <br>
(dated 2/3/2022) with the same flag set to 0, but with another line that <br>
says &quot;skip_if_unavailable=True&quot; This line is not present in the <br>
currently used file.<br></blockquote><div><br></div><div>Also, don&#39;t forget that \
you have to restart chrome after updating or you&#39;ll continue to see the \
notification.  </div></div></div>


[Attachment #6 (text/plain)]

_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@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/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


[prev in list] [next in list] [prev in thread] [next in thread]