On updating warp with dnf, both the autoupdate generated command and dnf update warp fail pgp check (Transaction failed: Signature verification failed. OpenPGP check for package warp.... from repo warpdotdev has failed: Problem occured when opening the package.). Downloading the package and manually installing doesnt help. I added the key with rpm from the url in the troubleshooting page, both as a file and from the url and i manually verified its in rpm. dnf clean all does nothing. This has been going on for several weeks, attempted the update at least 25 times on 5 separate days. I have no idea what else to try.
#Update PGP check fail
ionic jetty
tiny kestrelBOT
Hi @ionic jetty. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
This is a known and frustrating issue. Based on the knowledge sources, here are the steps that have worked for other users in similar situations:
For Fedora / RHEL / CentOS (dnf/yum)
The official troubleshooting page recommends refreshing the package signing key. [Updating Warp]
You can also try manually re-adding the repository and key using the full installation method. While the instructions below are documented for Debian/Ubuntu, several users on RPM-based systems reported success after fully re-adding the repo configuration. For your system, the equivalent would be:
cat <<EOF | sudo tee /etc/yum.repos.d/warpdotdev.repo
[warpdotdev]
name=warpdotdev
baseurl=<https://releases.warp.dev/linux/rpm/stable>
enabled=1
gpgcheck=1
gpgkey=<https://releases.warp.dev/linux/keys/warp.asc>
EOF
sudo rpm --import <https://releases.warp.dev/linux/keys/warp.asc>
sudo dnf upgrade warp-terminal
If That Still Fails
At least one user in the GitHub issues reported that removing and reinstalling Warp entirely resolved the OpenPGP check failure when nothing else worked. [Expired GPG Key]
If the Issue Persists
Since you've been experiencing this for several weeks across multiple attempts, and the standard troubleshooting steps haven't worked, I'd recommend:
- Filing or commenting on a GitHub issue — there are open/closed issues tracking this exact error (e.g., #8777, #8698) where Warp team members are actively responding. [OpenPGP check fail; Expired GPG Key]
- Include your logs when reporting, as the Warp team has specifically requested them to triage these signature verification failures.