Warp PGP key blocks pacman.

Open
#4,654 8 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
arch-linux, bash, rust
Domain
operating-systems, tooling

Research direction

No repository file, test, or entry point is identified in the report. Begin by reproducing the unknown-key and invalid-signature errors on Arch Linux with pacman, then trace the Warp package or repository configuration involved; done means pacman and yay can validate their databases without the Warp PGP key failure.

Written by the indexing model from the issue text.

Description

bug ready-to-implement triaged
Discord username (optional)

footerman.dev

Describe the bug

I've been using Warp for about a month now I think? No problems have happened until now. I attempted to install VirtualBox, but got these errors:

error: warpdotdev: key "19A1E427461B1795F73F629631F4254AFE49E02E" is unknown
:: Import PGP key 19A1E427461B1795F73F629631F4254AFE49E02E? [Y/n] y
error: key "19A1E427461B1795F73F629631F4254AFE49E02E" could not be looked up remotely
error: database 'warpdotdev' is not valid (invalid or corrupted database (PGP signature))

This also happens with AUR (yay).
I ran sudo pacman-key --refresh-keys, but that did not fix the issue. I have restarted terminal sessions, restarted my computer, removed the files using the commands here, nothing has fixed it.

To reproduce

No idea. I haven't messed with Warp's settings, AI or themes or anything much at all, I've just been using it as a normal terminal. I just ran the pacman command.

Expected behavior

Warp to not mess with the package manager.

Screenshots

image

Operating system

Linux

Operating system and version

Arch

Shell Version

bash 5.2.26

Current Warp version

v0.2024.02.20.08.01.stable_02 (I cannot change version)

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.)

No, this same issue happens in Warp and other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.