The bug was there when it was initially written. It was in 2003, which introduced PC/SC in rG1bcf8ef9dea1: Cleanups, fixes and PC/SC support
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 17 2022
When compiling the package, I can see that all 4 are applied.
May 16 2022
I have merged a contribution by Felix Tiede which adds support for publishing a key via WKS. It depends on KF5IdentityManagement, KF5MailTransport, and KF5MailTransportAkonadi. Those dependencies are optional. If they are not provided, WKS publishing is not available.
I think that it means that you only applied the last two patches.
Thanks for taking this up.
Thanks for your confirmation.
Thanks again for your update.
May 15 2022
May 14 2022
I just wrote a blog article about this problem
https://ludovicrousseau.blogspot.com/2022/05/scardlistreaders-and-non-initialized.html
Okay, confirmed: I was just wrong and the build failure was only ever with --disable-asm (i.e. the log in this bug is the only relevant one). Patch works.
May 13 2022
We meanwhile released two versions to our clients and are looking on how we can make it available to the community.
We have everything ready for a GnuPG Desktop Appimage but we first need a business case to maintain it.
We have a workaround by using a recent version of gpgtar directly. Thus lowering priority.
Please disable all other Add-Ins as well as extra security tools running on that machine to see whether there is some interference with them.
But only with an option - in general showing expired keys is annoying. For revoked keys the situation is different in case of a compromise - but many users revoke old keys anyway and we don't make use of the revocation reason. If we would consider the latter the UI/Support would be more complicated than useful.