Entering 4eb27db2a3b88b8b takes you to one key Linux Package Signing Key Īs you can see the package was signed with a completely different key.Ĭan search for a key. You can download this key using wget, and examine it: pub dsa1024/A040830F7FAC5991 The Key in your repo definition is to be found at So the package was signed with Key 4eb27db2a3b88b8b.

Now you have a copy of the package, you can check what key signed the You then have a chance to examine the issue.ĭnf -downloadonly -nogpgcheck install google-chrome-stable You can download the package with -nogpgcheck, and it will be Updating a package with -nogpgcheck is generally not a Good Thing ™ My temporary work-around was to manually update just the google-chrome-stable package with -nogpgcheck until I have a good understanding of the reason why this happened. But, I am diligent in keeping template packages up-to-date and the Chrome update failure blocked updates to other software that was concerning. Is that a correct assessment?Īctually, I only use Chrome in an appVM when it is absolutely necessary, which tends to be rarely. I’m thinking this is a Google Chrome issue unrelated to Qubes or Fedora. The GPG keys listed for the 'google-chrome' repository are already installed but they are not correct for this package.Ĭheck that the correct key URLs are configured for this repository. Sudo qubesctl -skip-dom0 -targets=fedora-37 -show-output state.sls update.qubes-vmĬomment: Problem encountered upgrading packages. Updates for google-chrome are failing with a complaint about an incorrect key for the package.

Google chrome update failed error 12