Oct 30 2023
In VS-Desktop-184.108.40.2068-Beta it is "no space left on device" now in the encrypt/verify window.
Oct 13 2023
The error message in Kleo is now (with VS-Desktop-220.127.116.11-Beta) "Broken pipe". But in the linked error protocol you can find the gpg error message "no space left on device". So I would find this message acceptable.
Oct 5 2023
Sep 27 2023
Sep 22 2023
I think there is a timing issue between the termination of a job and the retrieval of gpg's output, so that gpg's output is sometimes truncated or even completely empty. This is a general problem and not specific for this ticket.
works with VS-Desktop-18.104.22.168-beta214, too.
You are now informed that you do not have permissions to write there.
Kleopatra now shows:
Jul 4 2023
related to T6528
Jun 5 2023
Works in kleopatra; tested with gpg4win-4.2.0-beta339.
Jun 1 2023
I have set T6513: Kleopatra: Require GpgME 1.21 as blocker for this issue because, in my opinion, showing the above mentioned "Operation fully cancelled" error message is from a user perspective worse than showing multiple password prompts.
May 31 2023
Setting close_button when the user rejected the pin entry (by pressing the close button, the Cancel button or Esc) causes fully canceled. Unfortunately, Kleopatra (and in fact GpgME::Error) has no idea that fully canceled should be treated as canceled and not as error. Therefore, Kleopatra shows an ugly error message:
An error occurred while trying to change the passphrase for [...]:
Operation fully cancelled
May 30 2023
May 25 2023
The fix actually does the same as my suggested workaround.
May 17 2023
I see the problem: The Qt Pinentry does not implement the BUTTON_INFO status and thus we don't get a fully canceled error back (gpg-agent maps the cancel error to fully-cancel if the close button was used). Should be easy to fix in pinentry (set pinentry->close_button in the close eventhandler).