Test with gpg4win-Beta-50 shows the same as described in the last comment.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Oct 4 2024
tested with gpg4win-Beta-50:
works as described in https://dev.gnupg.org/T6866#179915
gpg4win-Beta-50:
Columns are now displayed as expected with a fresh installation, too.
Tested with gpg4win-beta-50:
Adding a subkey works, its possible to add A, E or S subkeys with different algorithms and expiration dates.
closing this ticket as duplicate as adding and changing expiry works.
Revocation of a single subkey is not yet possible in Kleopara, though
As we now have tabs for the subkeys this task is obsolete, really. Its useful as a parent ticket though.
Oct 2 2024
gpg4win 4.3.1 was with keyboxd, too. And vsd33 is only to mark that it would need to be backported for the next release (if this is a Kleopatra issue)
oh, I should have reloaded before commenting ;-)
In https://dev.gnupg.org/T7296#192032 you said you backported parts of T6666.
And the tooltips are in title case, currently, like Tobias said.
An improvement of the tooltips in this regard is not strictly necessary for the next release, though I admit it would be very nice.
But we need to add the "(except disabled ones)", which means a string change and if we are doing one change there, we should make all other changes to the tooltips in one go. Otherwise the translations would have to be done twice, too.
Oct 1 2024
with gpg4win-Beta-50 on a new (not upgraded) installation I see kleopatrarc in the folder %APPDATA%\kleopatra and kleopatragroupsrc in %APPDATA%\gnupg\kleopatra. And no kleopatra files in the base directory of %LOCALAPPDATA%.
works, the Root-CA of the above example is only shown once any more. Gpg4win-Beta-50
Deletion works, tested with gpg4win-Beta-50.
works, gpg4win-Beta-50.
The focus now stays on the selected line when you open e.g. a details window and close it again.
The testcase now works, gpg4win-beta-50.
I assume we do not want to unify this (yet)? But if we want to, we should make another ticket for this anyway.
Sep 30 2024
This issue is still valid in principle as of gpg4win-Beta-50 (and VSD Testversions for VSD 3.3).
Closing this ticket, as the test version is now obsolete and the new one much improved. I'll open a new one for the remaining issue with scdaemon when I have more information
I wonder if this has to do with T5960: Kleopatra: Encoding problems with GnuPG output on Windows as this is a recent regression. The Umlauts are ok in Gpg4win 4.3.1