I can't find any causes of slowness in keyboxd initialization. I think that there is a situation where it simply takes time on Windows.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 24 2025
Sep 23 2025
As there has been no more feedback on this for years, I'll close this.
Looks good to me on vsd-3.3.3-beta90.12 @ win10:
what ever was fixed with the attached commit we can not test.
I see no workaround.
The attachments in the original mail are not gone, yes.
But the mail can't be forwarded with them.
Tested with VS-Desktop-3.3.90.12-Beta, GpgOL 6.5 (WIN10 and WIN11)
2.2 test can be done with GnuPG-VS-Desktop-3.3.90.12-Beta-Standard.msi from Sep 17
Test with 3.3.90.12-Beta:
The test mail from before does not cause a spawn cycle and no high CPU load any more. (Tested without "show as text only", as it was not relevant before.)
Looks good to me on vsd-3.3.3-beta90.12 @ win10 (temporary filename is now attachment.odt or e.g. attachment (002).odt)
Debug log for vsd:
Also still present on vsd-3.3.3-beta90.12 @ win10 (mail is not moved)
Interesting. That means to replace hundreds of scripts in an average organization :-(.
@ametzler1 Thank you.
Sep 22 2025
Some data points:
The latest version of the standard (issue 8) has "The -a and -o binary primaries and the '(' and ')' operators have been removed." instead of "obsoleted" https://pubs.opengroup.org/onlinepubs/9799919799/utilities/test.html
After a discussion we decided to drop the idea to save the status of the check boxes even for only the box "encrypt for others".
Using gpg4win-5.0.0-beta369 @ win10 I can't reproduce it with use-keyboxd, but without use-keyboxd:
Current logs for a forever hang:
still reproducible on gpg4win-5.0.0-beta369 @ win10
In T6117#205379, @ikloecker wrote:I guess this is a typo because the CSR looks like an encryption-only certificate.
test -a is not a POSIX construct, I intentionally avoided it.
Sep 21 2025
Sep 20 2025
Sep 19 2025
Thanks for fixing this.
I think this will make the dialog less user friendly because with this change one always needs to check the status of all check boxes. Without the change the check boxes always have the same status when the dialog is opened the same way. Predictability is very important for usability and even more for accessibility.
I would like to change this ticket to "Save status of all check boxes in the sign/encrypt dialog".
ok, changed the text in the description of the ticket accordingly, but put two more "team" back in.