Confirming OpenPGP with a wrong key oops with no output

Bug #1947912 reported by Alexandre Gomes
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

When confirming an openpgp key if the user inputs text signed with an incorrect key launchpad just oops.

I was able to analyze the oops (https://oops.canonical.com/?oopsid=OOPS-cde01264bb18e3c177d06fe2ed81fce4) and found the key id was different from the one I was trying to confirm:
```
lp.services.gpg.interfaces.GPGKeyTemporarilyNotFoundError: GPG key D38C33334F9E8757 not found due to a server or network failure.
```

It would be useful for an end-user to receive a message error indicating the error "Key XXXXXXX not found".

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.