Arch Linux updater error
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 65.1k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Description
Discord username (optional)
No response
Describe the bug
This part fails: sudo pacman-key -r "linux-maintainers@warp.dev" --keyserver keys.openpgp.org
Output:
gpg: error retrieving 'linux-maintainers@warp.dev' via WKD: No data
gpg: error retrieving 'linux-maintainers@warp.dev' via keyserver: Server indicated a failure
gpg: error reading key: Server indicated a failure
==> ERROR: Remote key not fetched correctly from WKD or keyserver.
To reproduce
Click update warp and hit enter.
Expected behavior
No response
Screenshots
No response
Operating system
Linux
Operating system and version
Arch Linux
Shell Version
zsh 5.9 (x86_64-pc-linux-gnu)
Current Warp version
v0.2024.02.20.08.01.stable_01
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
No
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure through the “update warp” action on Arch Linux, then trace how it runs sudo pacman-key -r "linux-maintainers@warp.dev" --keyserver keys.openpgp.org. Use the reported WKD and keyserver errors to identify the updater path involved. Done means the update no longer fails while retrieving the signing key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arch-linux, zsh
- Domain
- operating-systems, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100