This came up in T6115 (https://dev.gnupg.org/T6115#173267 and following):
If a certification is already revoked it appears in Kleopatra as if a revocation happens anyway:
If it is not possible to recognize this before starting the revocation process (as discussed in the origin ticket) there should at least be no confirmation of the revocation which did not happen (again) or even an error message.
Probable cause: gpg status code is missing
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T6626 Kleopatra: Improve certification and revocation | ||
| Wontfix | • ebo | T6628 Kleopatra: Inform user if revocation of a certification does not happen |
I do not find this that important because while users tend to repeat actions to ensure that they are _really_ done (e.g. my nephew always saves games twice to ensure that it really was saved) no real harm is done here.
This issue does not occur on master, only on 2.2 and 2.4 branches.
So it will fix itself when we change to gpg 2.6.