Signature verification for Repository Google-Chrome failed error ( SUSE 15.0) .
by TYTA from LinuxQuestions.org on (#50999)
Hi all,
I have been running Suse 15.0 on my laptop and noticed that I don't get any software updates. When I choose "Software Updates" I get
Signature verification for Repository Google-Chrome failed error.
I tried command line and that is what I get:
Quote:
If I go "Yes", I still get the same Signature verification for Repository Google-Chrome failed next time I try to check for the update manually.
I would appreciate if someone helped me to fix the issue so that I can get the system updates again.
Warm Regards,
Alex
I have been running Suse 15.0 on my laptop and noticed that I don't get any software updates. When I choose "Software Updates" I get
Signature verification for Repository Google-Chrome failed error.
I tried command line and that is what I get:
Quote:
| alex@linux-co2:~> cat /etc/os-release NAME="openSUSE Leap" VERSION="15.0" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.0" PRETTY_NAME="openSUSE Leap 15.0" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.0" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" alex@linux-co2:~> alex@linux-co2:~> alex@linux-co2:~> alex@linux-co2:~> sudo zypper refresh Retrieving repository 'Google-Chrome' metadata ----------------------------------------------------------------------------------------------------------------------------------------------[|] Looking for gpg key ID 3CB3BD13 in cache /var/cache/zypp/pubkeys. Repository Google-Chrome does not define additional 'gpgkey=' URLs. Warning: File 'repomd.xml' from repository 'Google-Chrome' is signed with an unknown key '78BD65473CB3BD13'. Note: Signing data enables the recipient to verify that no modifications occurred after the data were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system and in extreme cases even to a system compromise. Note: File 'repomd.xml' is the repositories master index file. It ensures the integrity of the whole repo. Warning: We can't verify that no one meddled with this file, so it might not be trustworthy anymore! You should not continue unless you know it's safe. File 'repomd.xml' from repository 'Google-Chrome' is signed with an unknown key '78BD65473CB3BD13'. Continue? [yes/no] (no): |
If I go "Yes", I still get the same Signature verification for Repository Google-Chrome failed next time I try to check for the update manually.
I would appreciate if someone helped me to fix the issue so that I can get the system updates again.
Warm Regards,
Alex