Signature verification for Repository google-chrome-beta failed:
Software Update at the start of a session was working fine until yesterday when the google-chrome-beta repo started giving me a Signature Verification error.
Disabling and then enabling the repo in yast gave me the gpg error that one always gets when installing google chrome or the beta, but after answering the “Do you want to use it anyway” question with a positive, allows the refresh of repos to proceed fine.
Zypper dup does not give me the error with the repo enabled, and, my 2 Tumbleweed installs aren’t showing the error either. It’s only happening when using Software Update on Leap 15.1 from within KDE.
You can also change or remove and re-add the repository, re-accepting whatever keys are effective,
Although the Google instructions on the following page describes the usual method for all Linux distros, the second link from my Wiki describes how to “auto accept GPG keys” without all the work
Also present in TW, just a validation window in Yast asking to enroll the key.
This new pop-up for the missing Key is also present for Chrome Dev after installation in Yast. Answering yes, after re-opening Yast seems to work with the latest .RPM package. Never seen it before in TW, but present for a long time (Intermittent) for the .DEB package in Discover.
‘sudo apt-get --fix-broken install’ generates the key.