google-chrome-stable update fails today on gpg keys

[Neal Becker]

Today's dnf update fails with:

The GPG keys listed for the "google-chrome" repository are already
installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository..
Failing package is: google-chrome-stable-121.0.6167.184-1.x86_64
 GPG Keys are configured as:
https://dl.google.com/linux/linux_signing_key.pub

[Tom Horsley]

On Wed, 14 Feb 2024 07:46:15 -0500
Neal Becker wrote:

>  The GPG keys listed for the "google-chrome" repository are
> already
>  installed but they are not correct for this package. 
After getting this many times, I finally figured out I need to
manually run /etc/cron.daily/google-chrome to get new keys
(the install from the google rpm sets this up, but doesn't
always get run in time for the next update to work).

[Neal Becker]

On Wed, Feb 14, 2024 at 8:58 AM Tom Horsley <horsley1953(a)gmail.com&gt; wrote:

>  On Wed, 14 Feb 2024 07:46:15 -0500
>  Neal Becker wrote:
>
>  > The GPG keys listed for the "google-chrome" repository are already
>  > installed but they are not correct for this package.
>
>  After getting this many times, I finally figured out I need to
>  manually run /etc/cron.daily/google-chrome to get new keys
>  (the install from the google rpm sets this up, but doesn't
>  always get run in time for the next update to work).
>  --
>  
running /etc/cron.daily/google-chrome gives:

warning: Certificate A040830F7FAC5991:
  Policy rejects subkey 4F30B6B4C07CB649: Policy rejected asymmetric
algorithm
warning: Certificate 7721F63BD38B4796:
  Subkey 1397BC53640DB551 is expired: The subkey is not live
  Subkey 78BD65473CB3BD13 is expired: The subkey is not live
  Subkey 6494C6D6997C215E is expired: The subkey is not live

[Tom Horsley]

On Wed, 14 Feb 2024 09:06:44 -0500
Neal Becker wrote:

>  running /etc/cron.daily/google-chrome gives: 
I just ignore any gibberish it prints and do the update again,
always seems to work for me.

[Neal Becker]

On Wed, Feb 14, 2024 at 9:17 AM Tom Horsley <horsley1953(a)gmail.com&gt; wrote:

>  On Wed, 14 Feb 2024 09:06:44 -0500
>  Neal Becker wrote:
>
>  > running /etc/cron.daily/google-chrome gives:
>
>  I just ignore any gibberish it prints and do the update again,
>  always seems to work for me.
>  --
>  
Thanks!  Rubbish ignored.  I took those messages as errors, seems they are
just noise.

[Roger Wells]

This is happening to me as well.
uname  -r
6.8.9-200.fc39.x86_64
but
there is no /etc/cron.daily/google-chrome
(the directory exists but only contains google-earth-pro)

On 2/14/24 08:57, Tom Horsley wrote:
> On Wed, 14 Feb 2024 07:46:15 -0500
> Neal Becker wrote:
>
>> The GPG keys listed for the "google-chrome" repository are already
>> installed but they are not correct for this package.
> After getting this many times, I finally figured out I need to
> manually run /etc/cron.daily/google-chrome to get new keys
> (the install from the google rpm sets this up, but doesn't
> always get run in time for the next update to work).
> --
> _______________________________________________
> 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