On 2/21/26 8:08 AM, Tim Evans wrote:
On 2/14/26 11:23 AM, Frank Elsner via users wrote:
Hello all,
whats' behind this messages and how to solve the problem which "dnf -y
update"
suddenly shows?
[129/129] Total 100% | 3.0 MiB/s | 492.8 MiB
| 02m44s
[ 1/130] https://dl.google.com/linux/l ???% | 0.0 B/s | 0.0 B
| 00m00s
[ 1/130] https://dl.google.com/linux/l ???% | 0.0 B/s | 0.0 B
| 00m00s
[ 1/130] https://dl.google.com/linux/l 6% | 4.0 B/s | 1.1 KiB
| 01h07m
[ 1/130] https://dl.google.com/linux/l 100% | 48.0 KiB/s | 17.0 KiB
| 00m00s
--------------------------------------------------------------------------------
[130/130] Total 100% | 3.0 MiB/s | 492.8 MiB
| 02m44s
Transaction failed: Signature verification failed.
Public key "https://dl.google.com/linux/linux_signing_key.pub"; is
already present, not importing.
OpenPGP check for package "google-chrome-
stable-145.0.7632.75-1.x86_64" (/var/cache/libdnf5/google-
chrome-6ed7e4f336f6863c/packages/google-chrome-
stable-145.0.7632.75-1.x86_64.rpm) from repo "google-chrome" has
failed: Public key is not installed.
Have a nice weekend,
Frank
Curiouser and curiouser. A week later (specifically, yesterday
morning), this resolved itself on ONE of my systems.
Now, however, it's happening with the UNSTABLE version of Chrome.
On my other system, this now happens with BOTH versions of Chrome. That
is, neither will update.
Both systems are F43, fully updated. Main difference between the two
systems is the first has the fedora-updates-testing repo enabled.
I've tried both 'dnf re-install' and 'dnf remove,' followed by a fresh
install attempt
I don't know if this is related or not. Google-chrome-stable installs a
script in /etc/cron.daily. Recently this has been giving an error each
time it runs:
sudo /etc/cron.daily/google-chrome
warning: Certificate 7721F63BD38B4796:
Subkey E88979FB9B30ACF2 is expired: The subkey is not live
Comments in the script state:
# This script is part of the google-chrome package.
#
# It creates the repository configuration file for package updates, since
# we cannot do this during the google-chrome installation since the
repository
# is locked.
#
# This functionality can be controlled by creating the $DEFAULTS_FILE and
# setting "repo_add_once" to "true" or "false" as desired. An empty
# $DEFAULTS_FILE is the same as setting the value to "false".
and then the DEFAULTS_FILE has this:
cat /etc/default/google-chrome
repo_add_once="false"
I have not seen this reported here nor in the Fedora Discussion Forums
at https://discussion.fedoraproject.org/. Googling pulls up some old
reports. Looks like this has happened in the past. There's a variable
in the script called SUB_KEY_LIST and the best I can tell, they forgot
to add the current key to it. A key is supplied in the script.
Charlie
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
