On 23/10/23 02:25, Tim Evans 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.On 10/21/23 20:12, Stephen Morris wrote:On 11/10/23 21:59, Neal Becker wrote: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.On Tue, Oct 10, 2023 at 7:46 PM Tim Evans <tkevans@xxxxxxxxxxx> 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.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, Steve
Regards. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxxFedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelinesList Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Attachment:
OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
