The problem seems to have to do with the locking of the TOFU database.
Apr 9 2018
Feb 19 2018
Feb 16 2018
Still trying to pinpoint the bug, but I am afraid I am stuck.
Jan 29 2018
I did a few more tests and here are some more observations:
Jan 18 2018
One of these TOFU bugs. Thanks for the good bug report.
Dec 14 2017
You start Windows Explorer (the file manager thingy)
I feel dumb for asking this, but I'm a Mac guy, and my client is on Windows 10. How do I exactly "move away the data directory"?
Dec 13 2017
Ok I apologize for my ignorance as I've been desperate for help with not many places to turn to. Thank you very much
yes. That is the whole point of public key encryption. Please read one of the suggested intros or
ask for help at the firstname.lastname@example.org ML.
Ah man. So let me ask you for clarification in case I am not understanding this right. You're saying I encrypted the message with someone else's public key?
Dec 12 2017
Well, I meant to do this on the command line (cmd.exe). Replace INFILE with the name of the encrypted file and OUTFILE is the name of the file which will receive the decrypted data. You can't do that in the clipboard.
I included two pictures of what is going on. The first picture is what I get from trying to decrypt the line that you gave me. The second picture is the original issue I was having. I do appreciate your help
Can you please try to decrypt this message on the command line:
I also have had this problem. I just opened up my laptop for the first time in years. I was trying to decrypt text I encrypted years ago but I get that same error stated in the original post. Now I just remind you, this was encrypted years ago. In the encrypted message, after it says "begin pgp message," it says "version: GnuPg v2.0.20 (MingW32)" i am not sure if that matters, but that is all i have to give on my end other than i am currently using gpa 0.9.10 GnuPG 2.2.3
Please reopen or comment if that problem still happens if you move away the gnupg home directory.
Nov 27 2017
Nov 24 2017
@simypat Please try to move away GnuPG's data directory ( %APPDATA%\gnupg ) and start GPA again. That should fix it as the problem was a corruption of an internal database that lives in the Home directory (and is not removed when uninstalling).
Nov 22 2017
we uninstalled the old version, restarted, installed the new 3.01, and it still does the error
Nov 21 2017
@simypat, version 3.0.1 just hitted. I can't recreate this error anymore. Can you verify this?
Nov 17 2017
Should avoid the problem. Then import or create n OpenPGp key first and the next time you should(tm) not be bnotered by the bug.
Thank you Werner. Do you know when the next release will be? Is there a way for me to temporarily fix the current version in the code?
Nov 16 2017
This is verly likely be fixed with commit 5ecef193bc2144e6d51a6bd5727bfd08a0d28b66 which will be released with the next gpg4win version.
Oct 24 2017
Oct 19 2017
It is likely that gpa will be changed to always use the default algorithm. Users who have special requirements will need to use gpg on the command line.
Sep 13 2017
Fixed in master.
Sep 12 2017
I can replicate this even with master. Good catch.
Sep 11 2017
Aug 31 2017
Thanks. That reminds me again that a GPA release is due.
Jul 27 2017
Normally this error message can only come from gpgsm or dirmngr in case a certificate is listed that does have unsupported (unknown) critical extensions. Are you using X.509? What certificates do you have imported? You should be able to see the error and more information on the command line with "gpgsm -kv" and maybe some more options...
Jul 20 2017
Changing the message affects all translations.
Jul 13 2017
Landed in f7de6260936cafb5f56635956b55271baae72faf. Thanks!
Without more information, we can not act on this.
Jun 28 2017
No response for years.
Jun 22 2017
No response anymore, and we can not reproduce.
May 14 2017
Found the problem and fixed it. The Problem is described in the commit. Basically glib always assumed it gets UTF-8 Encoded filenames even if they were provided in system locale through double click / open with / command line / drag & drop.
Apr 24 2017
Added this to 3.0 because I don't want to release any known crashes.
Apr 4 2017
Mar 30 2017
Feb 8 2017
Hello. Im not that much of an expert. So Im not sure what kind of
information you need. But its Debian 8.7, amd64, Cinnamon, 16 GB ram
Or can you say what kind of information?
Today I freshly installed Debian 8.7.1 (latest stable), Gnome, amd64 using
VirtualBox with Windows 10 as the host, and then installed GPA on this
Debian. But it still has the same problem. Im boggled as to why I have this
We need more information how to reproduce the bug.
Jan 24 2017
Thanks for the report. The message you quoted is a very general error message,
and unfortunately does not really help identifying the problem.
Please describe in detail your setup, and how to reproduce this problem.
Jan 23 2017
0.9.10 was released in November
Jan 20 2017
Jan 13 2017
Nov 9 2016
Nov 8 2016
Oct 18 2016
Jul 18 2016
Fixed in 774dbffe.
Jul 11 2016
Jul 10 2016
Jul 8 2016
Jun 1 2016
$ gpg mBank17044.asc
pub rsa2048/375EB336C8086B9E 2015-01-19
uid AR17044 <XXXXXXXXXXXX@mbank.pl>
sub rsa2048/75E684B9017985DF 2014-12-29 [expires: 2016-01-20]
As you can see, the encryption subkey expired in January. Thus the holder of
the key does not want you to encrypt to this key after that date. We know that
GPA should give a better error message. I'll change your report to a wish to
Yes "unusable public key" (original message was not in English and obviously I
failed at translation...).
The key is valid (created at 2015-01-19, no expiration date) - you can see it
yourself, it's attached to this thread.
May 10 2016
May 3 2016
Please explain the version number you entered and from where you downloaded GPA