Keyserver issues are always hard to analyze because the state of the servers and which server you get is always a factor.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 1 2019
Sorry for the delay, I was on my summer vacation ;-)
Werner: I'm assigning this to you. Because the underlying reason is a missing status from gpg. I think we should add that for 2.3 as any new status line tends to break things.
can you please open the console (cmd.exe) and do a "gpg -K" and "gpgsm -K"
@joaociocca Can you please try to update to Gpg4win-3.1.9 and try again.
Jun 15 2019
Jun 11 2019
Hi,
as usual, thanks for your help.
The reason for this is the change to Kleopatra that the columns are configurable ( 4847fcc27afc8101752de82b0dd1f5fee027695d ). In the process we added additional columns like origin and to hide the "summary" column that the line edit for the recipients use we gave it an index number that was higher then our internal column count.
Thank you very much for the report. I can see this problem myself. It is strange because the code for that has not changed since 3.1.7 so it must be some sideeffect.
Jun 7 2019
File->Save As now works for crypto mails. It saves the encrypted message.
This works now, the hidden BeforePrint Event enabled us to detect when a print happens and the old code to do blocking decrypts enabled the actual printing.
We also do not print "our categories" (encrypted message, level x trust),... anymore, even in quick print.
Jun 6 2019
If it is that simple I really do not understand why this is not upstream. o.O
Just noticed that due to me failing to properly understand re-entrant locks the run-thread test is broken at least on windows in that it never waits for completion. So running out of filedescriptors is to expect. I'll fix the test.
My observation from running the verify threaded test on windows is that it does behave differently. The EBADF does not occur.
Jun 5 2019
Log loops with:
I have a hang now when keylisting in Kleo with GPGME_DEBUG=9:
Jun 4 2019
Just to clarify, you were able to decrypt and extract it without error? Which tool did you use to extract the tar archive?
The change in message class did not help.
Works for me
Jun 3 2019
Maybe the file was encrypted with a version of gpg4win-3.1.5? We had a serious bug there that sometimes files were corrupted. See: T4332