Since this is hard / impossible to test for, but the fix was obvious I am closing this directly. The fix for this is in GpgOL 2.5.12.

For the record. The code used to detect early on if the dark or bright icon theme should be loaded as a resource caused a crash during startup on at least Windows Server 2016 Enterprise. Our new fix avoids such API but I have created T6921: Kleopatra / Qt6: Improve accessibility detection for "Desert" high contrast scheme and fix it upstream to keep track of this since our fix is not fully complete in that it does not properly detect the Bright (Desert) High contrast mode and it should either be merged into KIconThemes or fixed in / with Qt6.

Also remove deprecated setup.py calls, use PEP517 style instead.

forgot the setup.py.in

• After two years, bump from serial 23 to 36
• Remove more distutils usage

https://github.com/vorburger/vorburger.ch-Notes/blob/develop/security/gpg-hangs-on-hostname-change.md

thats great news! I will test the keyword with Archlinux's Builds System (and Fakeroot) as soon as possible!

This is actually fixed already for the next version (with commit https://dev.gnupg.org/rKLEOPATRA655abf9a75e5f1cce8bc52b1cda21440970edfd7). The fix will just not be backported to VSD 3.2 to minimize the risk of another regression.

reopened. Because of reverted commits there is again no error message when trying to write to a write protected folder, see T6917.

moved to milestone 3.2.0, as 3.2.1 does not exist as column...

Works in VS-Desktop-3.1.91.9-Beta.

All non-archive jobs have been extended to allow reading the input directly from files and to allow writing the output. directly to files.

I sued the done column because we have not assigned it to any milestone.

Fixed a long time ago.

Hope so too. If there was a docker image or something I would gladly test it, otherwise I'll report back as soon as a release is out

We can't test this but assume that the fix for T6752 is sufficient here.

With rG239c1fdc28dcd0dc7aa5341be7c966da2231642a we now have a socketdir keyword for gpgconf.ctl. man gpgconf and look for that file. Will be released with 2.4.4.

gpg 2.4 now returns ERROR status lines for failed --quick-add-subkey and --quick-add-adsk.

Looks good except for a nitpick and some documentation.

Fix back in October, will be released in 24.02 megarelease.

There seems to be a problem with error reporting; errors from GPG (e.g., invalid password) are not coming through. I think this caused by GnuPG not reporting them correctly

Note that we now have also an option instead of the workaround from 2015