For our GnuPG Okular, we should not use the standard file names (okularrc, …) as this would conflict with a regular Okular installation.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 25 2025
Nov 24 2025
I wonder if we should better open a new ticket with all the relevant data when we get a report giving more information and set this one to invalid.
And meanwhile I have tested this a bit with VSD3.3.3 and in the case that the sender has a valid and *VS-compliant* key the automatic switching works.
Possibly include a preference for whether OpenPGP or S/MIME is checked first.
Nov 20 2025
The tool tip for the menu is missing.
And after the "Save at" dialog we here get a "Secrete Team key was saved to $PATH/$filename" notification window. The one for secret key backup has no location info and for public keys we have no message at all.
We should have consistent behavior when saving secret (and public) keys, imho.
Nov 18 2025
Nov 17 2025
works with Gpg4win-5.0.0-beta395, too
Nov 14 2025
@werner sees no reason to define a new status error for everything in gpg. So let's stick with this Kleopatra ticket and adding the "Audit Log"/"Diagnostics" button.
Yes, we now plan to add an "Show Audit Log" Button (or is it "Diagnostics" in this case?). But we are not sure if this is enough.
Nov 13 2025
it is probably not worth the effort to backport this
Note: We would need to handle possibly diverse error cases. A network share could be configured e.g. to not allow deletion for the user so that the temporary file can not be deleted.
meanwhile it looks like this in Kleopatra, it has now the blue sign but the issue is still the same:
what do we want here? "No public key" would be better that "General error" but then we would still have the same issue as here: T7886: Kleopatra: Enhance error on missing subkey, if set by default-new-key-adsk.
Nov 12 2025
Nov 11 2025
Nov 6 2025
This here is resolved, for timegrids findings see other ticket, the issue is not related to the one from this ticket and no regression, as it turned out. And difficult to trigger.
Nov 5 2025
Test with beta32
Nov 4 2025
Werner said we leave it as is for vsd3.3.3 and only change reading order of the configs for the change to the next mayor release.
So I retag this ticket for gpd5x. timegrid has made a separate ticket for updating the documentation.
Nov 3 2025
VS-Desktop-3.3.90.31-Beta shows no warning any more for the export of a newly generated key.
Oct 31 2025
And we shouldn't change the precedence in a minor release, I believe.
Oct 30 2025
Oct 29 2025
Well, in the audit log the output of gpg is shown, nothing Kleo can do there, I believe.
But we need to talk about what still needs to be / can be implemented on the Kleo side.
New ticket for the remaining issue.