Running TW on an AMD Gnome Wayland laptop. I’m getting the “Warning: Digest verification failed for file” error this morning when I run zypper.
Anyone else getting this error? Should I just try again tomorrow? Or is there something else I should do? Refresh the repos? (a google search suggested that)
I couldn’t find any recent forum posts on this topic.
Show the command you executed and the output you got, in code tags.
As always, this could well just be a matter of the mirrors syncing up, but without seeing the actual output you get and the command you ran, it’s impossible to say what the issue might be.
Also include the execution and output of zypper lr -d.
Whoops. I should have done that first. See below. Anything interesting?
advait@localhost:~> sudo zypper dup
[sudo] password for root:
Looking for gpg keys in repository snappy.
gpgkey=https://download.opensuse.org/repositories/system:/snappy/openSUSE_Tumbleweed/repodata/repomd.xml.key
Retrieving repository 'snappy' metadata -----------------------------------------------------------------------------------------------------------------------------------------------------------------[/]
Warning: Digest verification failed for file 'db0fd4d9e1bec726289648c0096b827ddbec02770a8be7b2327d3c46fa3afdf9c95e497c3b13b4354eaa39adf054209ea1f9a5f0a95da2876bae1aaabd74dd2f-filelists-ext.xml.gz'
[/var/tmp/AP_0xZDQ3Ok/repodata/db0fd4d9e1bec726289648c0096b827ddbec02770a8be7b2327d3c46fa3afdf9c95e497c3b13b4354eaa39adf054209ea1f9a5f0a95da2876bae1aaabd74dd2f-filelists-ext.xml.gz]
expected db0fd4d9e1bec726289648c0096b827ddbec02770a8be7b2327d3c46fa3afdf9c95e497c3b13b4354eaa39adf054209ea1f9a5f0a95da2876bae1aaabd74dd2f
but got 701fe2c3273a449958883a7de26d3d13fb86ce1c1fae9233f12a467c3631df19937e01877522e98f26c6148a4d16caaca982cdd7bb00de1562ff089ec6a13936
Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise.
However if you made certain that the file with checksum '701f..' is secure, correct
and should be used within this operation, enter the first 4 characters of the checksum
to unblock using this file on your own risk. Empty input will discard the file.
Unblock or discard? [701f/...? shows all options] (discard): ^C
Trying to exit gracefully...
advait@localhost:~>
Yes, my experience is that many of my Linux/TW issues fix themselves in a day or so. But I usually like to post a question in case there’s something important that I need to know. The extra info helps a noob like me understand Linux better.
If you are unsure about some basic zypper coomands, you can have a look at man zypper.
But yes, the above commands are safe (in opposite to some arbitrary GDrive links).
clean (cc) [options] [alias|name|#|URI] ...
Clean the local caches for all known or specified repositories. By default,
only caches of downloaded packages are cleaned.
-m, --metadata
Clean repository metadata cache instead of package cache.
-M, --raw-metadata
Clean repository raw metadata cache instead of package cache.
-a, --all
Clean both repository metadata and package caches.
refresh (ref) [alias|name|#|URI] ...
Refresh repositories specified by their alias, name, number, or URI. If no repositories are specified, all enabled repositories will
be refreshed.
See also METADATA REFRESH POLICY section for more details.
OK, I ran the two commands. Output below. The “sudo zypper ref” command triggered the same “Warning: Digest verification failed for file” error. Is the error connected with the Wireguard repo? I searched the forums for “Wireguard” but didn’t find anything relevant.
advait@localhost:~> sudo zypper clean --all
[sudo] password for root:
All repositories have been cleaned up.
advait@localhost:~> sudo zypper ref
Looking for gpg keys in repository Main Update Repository.
gpgkey=http://download.opensuse.org/update/tumbleweed/repodata/repomd.xml.key
Retrieving repository 'Main Update Repository' metadata ..............................................................................................................................................[done]
Building repository 'Main Update Repository' cache ...................................................................................................................................................[done]
Retrieving repository 'Google-Chrome' metadata .......................................................................................................................................................[done]
Building repository 'Google-Chrome' cache ............................................................................................................................................................[done]
Looking for gpg keys in repository Virtualization (openSUSE_Tumbleweed).
gpgkey=http://download.opensuse.org/repositories/Virtualization/openSUSE_Tumbleweed/repodata/repomd.xml.key
Retrieving repository 'Virtualization (openSUSE_Tumbleweed)' metadata ................................................................................................................................[done]
Building repository 'Virtualization (openSUSE_Tumbleweed)' cache .....................................................................................................................................[done]
Looking for gpg keys in repository Main Repository (NON-OSS).
gpgkey=http://download.opensuse.org/tumbleweed/repo/non-oss/repodata/repomd.xml.key
Retrieving repository 'Main Repository (NON-OSS)' metadata ...........................................................................................................................................[done]
Building repository 'Main Repository (NON-OSS)' cache ................................................................................................................................................[done]
Looking for gpg keys in repository Main Repository (OSS).
gpgkey=http://download.opensuse.org/tumbleweed/repo/oss/repodata/repomd.xml.key
Retrieving repository 'Main Repository (OSS)' metadata ...............................................................................................................................................[done]
Building repository 'Main Repository (OSS)' cache ....................................................................................................................................................[done]
Looking for gpg keys in repository google-chrome.
gpgkey=https://dl.google.com/linux/linux_signing_key.pub
Retrieving repository 'google-chrome' metadata .......................................................................................................................................................[done]
Building repository 'google-chrome' cache ............................................................................................................................................................[done]
Looking for gpg keys in repository microsoft-edge.
gpgkey=https://dl.google.com/linux/linux_signing_key.pub
Retrieving repository 'microsoft-edge' metadata ......................................................................................................................................................[done]
Building repository 'microsoft-edge' cache ...........................................................................................................................................................[done]
Looking for gpg keys in repository network:vpn:wireguard (openSUSE_Tumbleweed).
gpgkey=https://download.opensuse.org/repositories/network:/vpn:/wireguard/openSUSE_Tumbleweed/repodata/repomd.xml.key
Retrieving repository 'network:vpn:wireguard (openSUSE_Tumbleweed)' metadata ----------------------------------------------------------------------------------------------------------------------------[/]
Warning: Digest verification failed for file 'bb57af1fb6bf39535bab8d88495700714640ffae661e10b94d6664b163989ed85b3db228834478d6857f01a79e978e02bb7bfbcff0111062015aa5844f93228c-filelists-ext.xml.gz'
[/var/tmp/AP_0x5Vmmm4/repodata/bb57af1fb6bf39535bab8d88495700714640ffae661e10b94d6664b163989ed85b3db228834478d6857f01a79e978e02bb7bfbcff0111062015aa5844f93228c-filelists-ext.xml.gz]
expected bb57af1fb6bf39535bab8d88495700714640ffae661e10b94d6664b163989ed85b3db228834478d6857f01a79e978e02bb7bfbcff0111062015aa5844f93228c
but got 701fe2c3273a449958883a7de26d3d13fb86ce1c1fae9233f12a467c3631df19937e01877522e98f26c6148a4d16caaca982cdd7bb00de1562ff089ec6a13936
Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise.
However if you made certain that the file with checksum '701f..' is secure, correct
and should be used within this operation, enter the first 4 characters of the checksum
to unblock using this file on your own risk. Empty input will discard the file.
Unblock or discard? [701f/...? shows all options] (discard): ^C
Trying to exit gracefully...
advait@localhost:~>
5700g:~ # zypper if wireguard
Looking for gpg keys in repository wireguard.
gpgkey=https://download.opensuse.org/repositories/network:/vpn:/wireguard/openSUSE_Tumbleweed/repodata/repomd.xml.key
New repository or package signing key received:
Repository: wireguard
Key Fingerprint: 426A A6B0 285C 2096 B70D 9FC2 5284 23A4 69A7 7D9A
Key Name: network OBS Project <network@build.opensuse.org>
Key Algorithm: RSA 4096
Key Created: Tue Jun 17 10:04:08 2025
Key Expires: Thu Aug 26 10:04:07 2027
Rpm Name: gpg-pubkey-69a77d9a-68512178
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: A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If
you are not sure whether the presented key is authentic, ask the repository provider or check
their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they
are using.
Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): a
Retrieving repository 'wireguard' metadata ...........................................................................................................................................................................................[done]
Building repository 'wireguard' cache ................................................................................................................................................................................................[done]
Loading repository data...
Reading installed packages...
Information for package wireguard:
----------------------------------
Repository : wireguard
Name : wireguard
Version : 1.0.20200401-40.2
Arch : x86_64
Vendor : obs://build.opensuse.org/network
Installed Size : 18.0 KiB
Installed : No
Status : not installed
Source package : wireguard-1.0.20200401-40.2.src
Upstream URL : https://www.wireguard.com/
Summary : Fast, modern, secure kernel VPN tunnel
Description :
WireGuard is a novel VPN that runs inside the Linux Kernel and uses
state-of-the-art cryptography (the "Noise" protocol). It aims to be
faster, simpler, leaner, and more useful than IPSec, while avoiding
the massive headache. It intends to be considerably more performant
than OpenVPN. WireGuard is designed as a general purpose VPN for
running on embedded interfaces and super computers alike, fit for
many different circumstances. It runs over UDP.
5700g:~ #
Obviously you are diverted to a mirror out of sync.
On this side you see all the mirrors and not one. You have to choose one near by you and goto the oprator field and then down to your preferd mirror.
Add it with myrlyn.
Myrlyn says I need to refresh before using Myrlyn. But sudo zypper ref gets error before completing. Catch 22. See below. How to fix this?
Now it appears the “snappy” repo is messed up.
advait@localhost:~> sudo zypper ref
[sudo] password for root:
Repository 'Main Update Repository' is up to date.
Repository 'Google-Chrome' is up to date.
Looking for gpg keys in repository Virtualization (openSUSE_Tumbleweed).
gpgkey=http://download.opensuse.org/repositories/Virtualization/openSUSE_Tumbleweed/repodata/repomd.xml.key
Retrieving repository 'Virtualization (openSUSE_Tumbleweed)' metadata ................................................................................................................................[done]
Building repository 'Virtualization (openSUSE_Tumbleweed)' cache .....................................................................................................................................[done]
Looking for gpg keys in repository Main Repository (NON-OSS).
gpgkey=http://download.opensuse.org/tumbleweed/repo/non-oss/repodata/repomd.xml.key
Retrieving repository 'Main Repository (NON-OSS)' metadata ...........................................................................................................................................[done]
Building repository 'Main Repository (NON-OSS)' cache ................................................................................................................................................[done]
Looking for gpg keys in repository Main Repository (OSS).
gpgkey=http://download.opensuse.org/tumbleweed/repo/oss/repodata/repomd.xml.key
Retrieving repository 'Main Repository (OSS)' metadata ...............................................................................................................................................[done]
Building repository 'Main Repository (OSS)' cache ....................................................................................................................................................[done]
Repository 'google-chrome' is up to date.
Repository 'microsoft-edge' is up to date.
Repository 'Packman Extras (Mesa)' is up to date.
Repository 'Open H.264 Codec (openSUSE Tumbleweed)' is up to date.
Looking for gpg keys in repository snappy.
gpgkey=https://download.opensuse.org/repositories/system:/snappy/openSUSE_Tumbleweed/repodata/repomd.xml.key
Retrieving repository 'snappy' metadata -----------------------------------------------------------------------------------------------------------------------------------------------------------------[/]
Warning: Digest verification failed for file 'c65f86a0dc27f0d9618aa189545257c72074f5e4fe155b904c6dc67fe66fa68ab9a4deddf1d701a28c6ff3a52bf63d17bef8cf15057e8a9216c00cf241d131c4-filelists-ext.xml.gz'
[/var/tmp/AP_0xjCXizl/repodata/c65f86a0dc27f0d9618aa189545257c72074f5e4fe155b904c6dc67fe66fa68ab9a4deddf1d701a28c6ff3a52bf63d17bef8cf15057e8a9216c00cf241d131c4-filelists-ext.xml.gz]
expected c65f86a0dc27f0d9618aa189545257c72074f5e4fe155b904c6dc67fe66fa68ab9a4deddf1d701a28c6ff3a52bf63d17bef8cf15057e8a9216c00cf241d131c4
but got 701fe2c3273a449958883a7de26d3d13fb86ce1c1fae9233f12a467c3631df19937e01877522e98f26c6148a4d16caaca982cdd7bb00de1562ff089ec6a13936
Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise.
However if you made certain that the file with checksum '701f..' is secure, correct
and should be used within this operation, enter the first 4 characters of the checksum
to unblock using this file on your own risk. Empty input will discard the file.
Unblock or discard? [701f/...? shows all options] (discard): ^C
Trying to exit gracefully...
advait@localhost:~>