Bad GPG signature found: /var/cache/PackageKit/41/metadata/NetBird-41-x86_64/packages/netbird_0.35.2_linux_amd64.rpm could not be verified. /var/cache/PackageKit/41/metadata/NetBird-41-x86_64/packages/netbird_0.35.2_linux_amd64.rpm: digest: SIGNATURE: NOT OK
Fedora linux update:
Bad GPG signature found:
/var/cache/PackageKit/41/metadata/NetBird-41-x86_64/packages/netbird_0.35.2_linux_amd64.rpm could not be verified. /var/cache/PackageKit/41/metadata/NetBird-41-x86_64/packages/netbird_0.35.2_linux_amd64.rpm: digest: SIGNATURE: NOT OK
I have the same issue
Also have the same problem. This prevents system updates on Fedora.
Used the guide on "RPM/Red hat/Amazon Linux 2" in install docs to install NetBird.
Temporary solution:
If you stop the service --> uninstall service --> uninstall NetBird client, you will be able to install the Fedora updates. You are then able to reinstall the NetBird service and client.
This happens for me when updating through Fedora's Discover software centre.
Bad GPG signature found:
/var/cache/PackageKit/41/metadata/netbird-41-x86_64/packages/netbird-ui_0.38.2_linux_amd64.rpm could not be verified.
/var/cache/PackageKit/41/metadata/netbird-41-x86_64/packages/netbird-ui_0.38.2_linux_amd64.rpm: digest: SIGNATURE: NOT OK
I have found that using the console and sudo dnf update directly will perform the upgrade successfully, so there is no need to uninstall/reinstall each time, at least for me. Still it would be better to have a proper fix.
Can you confirm if there is any custom setting for our repository in your system? The RPMs aren't signed yet, which causes the check to fail as expected, but our examples shouldn't have the check enabled either.
My /etc/yum.repos.d/netbird.repo looks like this:
[netbird]
name=netbird
baseurl=https://pkgs.netbird.io/yum/
enabled=1
gpgcheck=0
gpgkey=https://pkgs.netbird.io/yum/repodata/repomd.xml.key
repo_gpgcheck=1
and it has been created with curl -fsSL https://pkgs.netbird.io/install.sh | sh.
I have however found tailscale/tailscale#6246 which suggests this might be a problem with Discover. There are some other reports about this, but it doesn't seem to go anywhere as far as I could find (for example).
Same problem on Fedora 41. Discover can't update packages, but Gnome Software can (it shows dialog, asking what to do with this packages).
Any news on how to resolve this?
Through Discover I receive this error, but when I do dnf update, it says that there are no new files to update? The NetBird icon, however, shows that there is a new update - its very confusing.
This should be fine for most cases, but maybe something fails on different systems using DNF, see the example below with a fedora container; see highlighted text with a similar error, but dnf handles it:
DNF in the terminal handles it but PackageKit via Discover won't. That means the updates on desktop systems are broken when the GPG key needs to be imported. Ideally it shouldn't need to be imported every update.
I have this same issue on fedora, has there been any change to this?
I have however found tailscale/tailscale#6246 which suggests this might be a problem with Discover.
It looks like they fixed the issue by signing the packages, see tailscale/tailscale#1882.
I still have this issue. Seems doing:
sudo dnf update
works fine but it uninstalls and reinstalls netbird to update it.