We decided to remove one more item:
- Copy to card
Because it is only doe once, usually.
We decided to remove one more item:
Because it is only doe once, usually.
The reporter in the forum originally wrote:
We need a better error code from gpg to change this
We decided that gpg should emit a status message for success, too.
gpgme should then look for that status message instead of only absence of error.
Although in VSD 3.2.2 we get no warning when configuring S/MIME debugging wrong we then get a nice message "Configuration error" when trying to encrypt with S/MIME, instead of gpgsm hanging without any message at all:
The issue also occurs in VSD-3.3.2 and 4win-4.4.1 but not in VSD 3.1.26
works in vsd3.3.3, tested with VS-Desktop-3.3.90.8-Beta
OK on Linux now with new enough versions (Fedora 42).
Tested with Fedora 42 (which includes gpgme 1.24.3): this works now, you can drag a public or secret key from Kleopatra to a file manager to export the public key.
Finally came around to check this.
On Fedora with Kleopatra 25.04.03, gpg 2.4.5 and pinentry 1.3.1 the pinentry window ist above the Kleoaptra windows.
closing, rest in follow up ticket.
Turns out the cause is a wrong entry in the gpgsm.conf. Setting "dbug-level basic" without specifying an output file.
And encrypting a file is likewise affected.
Closing this ticket, the task is done. Further improvements should go into a new tickets after we decided what we want.
Ok, setting this to done, but not resolved so that timegrid will notice it and make a new ticket with more information for the "no data" message.
well the messages are improved, if we want to improve them further, this should go into a new ticket.
I assume you only forgot to move this to testing, as this is solved.
We now have separate windows for the notepad, several ones can be opened now.
Checked with Gpg4win-5.0.0-beta357
tested with Gpg4win-5.0.0-beta357 (GnuPG 2.5.11):
next version:
Besser: The signing certificate is not certified by you or a trusted person.
not sure if this really is an issue, maybe for a person proficient with a a screenreader the behavior ist ok, after the fix of the show/hide button is done?