This might be related to the recent changes in now we spawn processes. Using gpgtar [...] --status-fd=3 3>a.log shows something different than directly using --status-fd=2. Do we handle the process termination correctly; i.e. wait for all status-fd output?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 30 2025
well the messages are improved, if we want to improve them further, this should go into a new ticket.
I assume you only forgot to move this to testing, as this is solved.
We now have separate windows for the notepad, several ones can be opened now.
Checked with Gpg4win-5.0.0-beta357
Some lines from the log:
2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] DECRYPTION_KEY 46ED5D7758C1BD71C27AF928 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: FFA2FCCB2EC589F8 98111E67AE06F2BEFD2BDE10C5D6C91 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: 9005F36A4 u<LF> 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] BEGIN_DECRYPTION<LF> 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] DECRYPTION_INFO 2 9 0 0<LF> 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] PLAINTEXT 62 1753871344 <LF> [...] 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] NEWSIG<LF> [...] 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] KEY_CONSIDERED F8D51DE0EE16E9B57009B8DE 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: 458612006D8E6F0D 0<LF> [...] 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] GPGTAR_EXTRACT 2 0 0 0 0 0 0<LF> [...] 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] SUCCESS<LF> [...] 2025-07-30 12:35:29 gpgme[716.808] gpgme:reader: check: ctx->hdd=0x000001b90c8a6a60 got EOF (broken pipe) [...] 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_cancel_with_err: enter: ctx=0x000001b90c854430 ctx_err=117440570, op_err=0 [...] 2025-07-30 12:35:29 gpgme[716.1e08] gpgme:reader: check: ctx->hdd=0x000001b90c8a68c0 got EOF (closed by us) [...] 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_op_decrypt_ext:186: error: No data <GPGME>\n 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_op_verify_result: enter: ctx=0x000001b90c854430 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_op_verify_result: leave: result=0x000001b90c7d1150 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_get_protocol: call: ctx=0x000001b90c854430 ctx->protocol=0 (OpenPGP) 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_op_decrypt_result: enter: ctx=0x000001b90c854430 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_op_decrypt_result: check: ctx=0x000001b90c854430 result: recipient: keyid=FFA2FCCB2EC589F8, pubkey_algo=302, status=Success 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_op_decrypt_result: leave: result=0x000001b90c5e3290
-> there's a broken pipe; _gpgme_cancel_with_err has ctx_err 117440570 = (GPGME, No data)
-> gpgme_op_decrypt_ext reports an error: No data <GPGME>\n
-> There doesn't seem to be a verify result (although the archive is signed and encrypted)
-> There is a decrypt result with status Success
I had a quick look at the status messages that gpg emits. Unfortunately, gpg doesn't emit a status message after successfully signing a key. So, we may have to check whether the signed key really has a new certification to ensure that the operation succeeded. And we should make future version of gpg emit a success status.
Jul 29 2025
Ideally, this will be solved for VSD 3.4.
Jul 28 2025
Jul 25 2025
next version:
Besser: The signing certificate is not certified by you or a trusted person.
Regarding the "Keine Daten" on corrupted message: the diagnistics says e.g.: "gpg: Prüfsummenfehler; c83745 - f75c60"
Looks good to me on gpg4win-5.0.0-beta345 @ win10
Looks good to me on gpg4win-5.0.0-beta345 @ win10
Looks good to me on gpg4win-5.0.0-beta345 @ win10
Looks good to me on gpg4win-5.0.0-beta345 @ win10
Looks good to me on gpg4win-5.0.0-beta345 @ win10
Looks good to me on gpg4win-5.0.0-beta345 @ win10
On gpg4win-5.0.0-beta345 @ win10 the progress bar is shown:
Ah, i missed the description edit. Then it looks good to me.
Looks good to me on gpg4win-5.0.0-beta345 @ win10
seems not to be included in gpg4win-5.0.0-beta345 yet
Jul 24 2025
Other duplicate texts:
- Enter some characters for Password and some other characters for Repeat and press Return.
- Message box pops up to inform user that the two entered texts don't match. NVDA reads
does not match - try again dialog OK button Enter (not audible) does not match - try again dialog
This has been fixed in pinentry-qt5 (which is used by VSD 3.x).
Another suggestion for the changed button text was simply "List Certificates" as the context implies which those will be. I like it.
Jul 23 2025
tested with Gpg4win-5.0.0-beta345
Done.
Jul 22 2025
Backported for VSD 3.4
not mentioned in the test for v3.1.26, and checksums are no important part of the software
Done for gpg4win 5 and backported for VSD 3.4 (provided that the gpg4win-4-branch will be used for VSD 3.4).