On 2/22/26 4:08 AM, Tim via users wrote:
On Sat, 2026-02-21 at 08:53 -0500, Charles Dennett wrote:
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"
If you're prepared to look after daily updates yourself, you could
remove it.
On an old Mac, I had to remove Google, it would wedge the system trying
to update itself, and complain that it couldn't. Removing the browser
wasn't enough, I had to delve into its google-updater that it'd
installed, too.
I don't know... multinational corporations that can't get their act
together... They have enough money to employ competent staff, and do
proper testing before release.
YMMV, but the following procedure did update google-chrome-stable (and
-unstable) here, although I don't understand it and am not sure it fully
completes the task.
1. Run dnf update as usual; it will fail with the signature verification
error we have seen. (All other updates in the batch also fail to
install, as we have seen--do NOT re-run dnf with the --exclude flag.)
2. Re-start your system. Do not do anything before doing so, in
particular do not 'dnf clean.' (This leaves the
downloaded-but-not-installed updates in the dnf cache.)
3. Anwser yes to the "install pending updates" pop-up. System starts to
reboot.
4. Previously downloaded updates in the dnf cache, including
google-chrome* install duing the reboot; I did not see any signature
verification messages during this process. System may reboot a second time.
I don't know, of course, what will happen with the next google-chrome
update.
--
_______________________________________________
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
