The table is now (more) accessible. The second issue doesn't apply anymore because of T6108: Kleopatra: Information on storage location of OpenPGP key should be per subkey.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jul 27 2022
Hi Marcel!
I just confirmed that firmware 5.4.3 works fine with the changes (to be 2.2.37 and 2.3.8).
Sure... it's really more of a cosmetic issue. Even without verbose mode, it should become quickly clear to anyone.
New release of libassuan is expected to make sure it's cleared off.
What I found: When the page is served by the server, it omits "charset=utf-8" part. This is the issue.
Jul 26 2022
I used to have the option of generating PGP Keys up to 4,096 key size. That function has completely disappeared.
Probably fixed meanwhile in 2.2.
Please re-open if experience this problem also with a decent gnupg 2.2 versions.
Probably an invalid specified keyserver
- Tables need to work with TAB focus and then arrow button navigation
Issues:
- Fingerprint is inaccessible (finding [3] in the Prüfbericht Barrierefreiheit GnuPG Kleopatra 3.1.20.3)
- "Certify with" label not associated with combo box
- Collapsible "Advanced" section is not accessible (announced as "check box")
- UI elements in "Advanced" section can receive focus, even if section is collapsed (finding [12] in the Prüfbericht Barrierefreiheit GnuPG Kleopatra 3.1.20.3)
- "Tags" label not associated with input field
- Pressing Esc cancels dialog even if explanation tooltip is shown
- "Domain" input field has no label (finding [4] in the Prüfbericht Barrierefreiheit GnuPG Kleopatra 3.1.20.3)
- No accessible feedback when checking/unchecking user ID
Thanks for fixing.
That is not easy to change because we show all kind of error codes. If you run in --verbose mode you should see more info.
There won't be any semantic changes for obvious reasons.
Thanks for reporting.
The first thing is a problem of the GNU makeinfo tool. Can't be fixed int the source.
The fix has been merged to the 2.2 branch.
Jul 25 2022
For documentation purposes: Werner suggested to use a TCP socket on Windows for logging (on the mailing list).
Should be much more accessible now. Only tested with orca which has its own quirks.
Please ask your card vendor.
Jul 23 2022
Jul 22 2022
@gniibe Thanks!
In the repo, for all related software, it's done.
Note that versions since 2020-11-07 to 2021-07-03 have major problem with non-POSIX shell, which doesn't support $(..) construct.