Related, the tab formatting (mixed first one tab and then space), as in lines 131 to 137 of src/icons.c _really_ causes headaches.

Release today.

Just commited. Thanks.

The next version will have a details button to show the actual gpg output. This will often be helpful.

The current version is 0.9.10 and the reported 0.9.5 is 4 years old. We also received no more info.

The "Copy" menu item already copies public keys to the clipboard.
I now added a private key key copy option to the context menu.

Sorry, I meant the key pair (thought bundle) of private and public key.

I am not sure what you mean by “keybundle”. Is is a single keyblock or a selection of multiple keyblocks?

This is still true even after the latest changes to GpgOL not to require Kleopatra or GPA through the UIServer protocol. The details dialog / search still uses Kleopatra or GPA as a fallback.

Linux, Ubuntu

Is that on Windows?

The use of --textmode is in general not a good idea. The GPA on Windows will work just fine regardless of line endings. Notepad.exe also does not care about line endings as does other proper text handling software. If there is a problem c+p from the GPA "clipboard" do the system clipboard we can fix that.

Thanks @werner for applying the patch. Closing here, since I have been using that patch for several weeks now without ever encountering the bug again.

The problem seems to have to do with the locking of the TOFU database.

Still trying to pinpoint the bug, but I am afraid I am stuck.

I did a few more tests and here are some more observations:

One of these TOFU bugs. Thanks for the good bug report.

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"?

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 gnupg-users@gnupg.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?

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.

@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).

we uninstalled the old version, restarted, installed the new 3.01, and it still does the error

@simypat, version 3.0.1 just hitted. I can't recreate this error anymore. Can you verify this?

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?

This is verly likely be fixed with commit 5ecef193bc2144e6d51a6bd5727bfd08a0d28b66 which will be released with the next gpg4win version.

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.

Fixed in master.

I can replicate this even with master. Good catch.

Thanks. That reminds me again that a GPA release is due.

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...

Changing the message affects all translations.

Landed in f7de6260936cafb5f56635956b55271baae72faf. Thanks!

Without more information, we can not act on this.

No response.

No response for years.

No response anymore, and we can not reproduce.

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.

Added this to 3.0 because I don't want to release any known crashes.

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
problem.

We need more information how to reproduce the bug.

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.

0.9.10 was released in November

Fixed in 774dbffe.

Thanks!

$ gpg mBank17044.asc
pub rsa2048/375EB336C8086B9E 2015-01-19
uid AR17044 <XXXXXXXXXXXX@mbank.pl>
sub rsa2048/75E684B9017985DF 2014-12-29 [expires: 2016-01-20]

[uid redacted]
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
implement this.