A quick check with passing ASSUAN_PIPE_CONNECT_DETACHED does not changed anything.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 13 2025
Aug 12 2025
I wonder whether rA3bccb33ccd9028ff505d9979fd6c8a37393b892d which changes Assuan's waitpid function for Windows is well aligned with the my_waitpid in gpgme's assuan-support.c (which does nothing). gpgme creates a detached process in most cases but for gpgsm assuan_pipe_connect is used without the ASSUAN_PIPE_CONNECT_DETACHED flag.
Another data point is that the faulty versions use libassuan 3 with a slightly changed API. May one of the follwing chnages cause the problem?
Aug 11 2025
Although in VSD 3.2.2 we get no warning when configuring S/MIME debugging wrong we then get a nice message "Configuration error" when trying to encrypt with S/MIME, instead of gpgsm hanging without any message at all:
Logging all
Someone should test whether gpgol2 is able to reencrypt all subfolders of a given folder. The file reencrypt tool (current name "recipients" "hugh") does this already.
The patch above is wrong for if (!rc) last_err = rc;, the condition should be (rc).
It's in master (to be 1.12), then, it's backported to 1.11.2, which is confirmed build well.
So, closing.
Aug 10 2025
Thanks for testing.
Aug 9 2025
Hello,
thank you all. I can confirm that 1.11.2 builds successfully on ppc64el with gcc-15 (Debian sid + experimental). Lacking access I have not be able to check alpha. I would suggest closing this report as fixed.
cu Andreas
Aug 8 2025
The issue also occurs in VSD-3.3.2 and 4win-4.4.1 but not in VSD 3.1.26
Aug 7 2025
works in vsd3.3.3, tested with VS-Desktop-3.3.90.8-Beta
OK on Linux now with new enough versions (Fedora 42).
Tested with Fedora 42 (which includes gpgme 1.24.3): this works now, you can drag a public or secret key from Kleopatra to a file manager to export the public key.
Fixed and backported for VSD 3.4
Aug 6 2025
Solved by focusing the result message after the notepad operation is complete. I think that's an acceptable compromise for ensuring that users of assistive tools are informed about the result even if the focus is moved to a different UI element (which, in general, should be avoided because users can get lost).