Btw. this was patched in Gpg4win for over a year now. So I expect we would have
heard if this caused regressions.

I've opened T2185 for the GPA Problem so i can change the topic here and we
can cleanly close this issue when the gpgtar fix is applied upstream.

We might also want to create a new fix for UTF-16 support in gpgtar once this is
closed. But the attached patch would improve the current situation already a lot.

snicker: I'm sorry it's been so long since you've gotten a response.

Are you still getting these crashes? If so, it would be good if you could run
gpa under gdb. Then, when it crashes, you should be able to get a backtrace
using: 'bt full'

$ gdb ../gpa.exe
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ../build/gnupg/g10/t-keydb...done.
(gdb) run
Starting program: ...

Program received signal SIGABRT, Aborted.
0x00007ffff7149107 in __GI_raise (sig=sig@entry=6)

at ../nptl/sysdeps/unix/sysv/linux/raise.c:56

56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt full
...

Please provide attach the full output to this bug report.

Unfortunately, I don't use Windows so I can't provide more exact instructions.
I hope Andre will correct any details I've gotten wrong.

Fix in ea99f88.

Please describe which certifciates you see, which version of GnuPG you are
using, and what error you get when trying to delete a cert.

to be released with 0.9.10

Fixed with commit d06a5f5.

IT has nothing to do with the long user id. You can't delete any X.509 key.
GPA uses gpgsm to delete this key - I have to debug this.

Which version of GnUPG are you using. The GPA About window shows the gnupg
versions. If you can't access that, please run "gpgconf --version".

Which version of gpgme are you using ("gpgme-config --version")?

here is the the brooad key, which cannot be deleted.

I just tried to delete a key wirth a long uid without problems.
Can you please provide a public key which exhibits this problem (bey pPM if you
prefer)

gpa 0.9.9 has been released with this fix.

This issue seems fixed in gnupg-w32-2.1.7.

Okay, it is fixed in the repo. The user ids are truncated but a tooltip shows
them untruncated.

I can't reproduce this. I've tried running gpa for several days in a Vbox and
doing crypto operations now and then. It never crashes.

This on Windows 10 32bit.

On 08/27/2015 06:21 PM, Werner Koch via BTS wrote:

Hey, why are you adding an X.509 DN to the key?

It's not my key - I do not even know how to do that ;)

Hey, why are you adding an X.509 DN to the key?
Anyway, we need to truncate too long user names.
Thanks.

On 08/27/2015 03:55 PM, Werner Koch via BTS wrote:

Werner Koch <wk@gnupg.org> added the comment:

What do you mean by "remove"? "delete key"?

What do you mean by "remove"? "delete key"?

Can you please try with the latest gpg4win version? We have not fixed any bug
leading to a crash but some libraries have been updated, so it would be good to
get a confirmation that there is still a problem.

I would also suggest to try it under a new user account to avoid problems with
already existsing keys. What other software are you using on your machines -
something must be uncommon in your installation.

Can you still replicate this with gnupg-w32-2.1.7 ?

Please read http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
and give us some more information.

Error reporting will be better with GnuPG 2.1.8.
To triage the bug we need a bit more information. If you can still reproduce it
with the latest gpg4win, please send a description after having read
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Fixed with commit 071ed43. Will go into 0.9.8.

Sorry for delaying it for so long.

It probably would have been better to create two issues:
a) Dataloss with Kleo in 2.2.2 (fixed now)
b) crash with gpa

The latest version is 0.9.7. Please report error only against the latest version.
It has likely been fixed.

Could this case please get some attention. This is still an issue for me and
everyone else I know using GPA for windows. Can I help with any more information?

Several such bugs have been fixed in the meantime. I can't repeat it anymore.

The context menu of the key manager now has a "refresh key" item.

Yes, it is part of the gpg4win, it is the latest version. 2.2.3 but the last
versions also have the same problem.

From where did you get the gpa.exe - was it part of gpg4win; if so which version?

I've changed the category to gpa, adjusted the topic and version to 2.2.3
As you've already described the problem together with GPA here I think this is
better then opening a new bug.

I'll also no longer call this critical as the original data loss problem
(Encrypting files where one has an umlaut -> kleo thinks its a success and
deletes the original) Should be resolved.

The fix in GPA should be fairly easy. Some conversion from native to utf-8 on
input and utf-8 to native on output. So I'm taking this issue.

Werner: Could you please take a look at the patch for gpgtar. I will probably
propose something quite similar for GPA. Not real unicode support but at least
for 8 bit filenames.

0.9.6 will be release today, thus I close it.

GNOME--

It's not crashing for me with master but its not fixed.

I acidentally ran into this while checking out a windows crash and found the cause:
echo $GPG_AGENT_INFO /run/user/1000/keyring-Lvs93w/gpg:0:1

At least this was my problem and as "Ubuntu" is the platform it is likely that
this was the original problem.

I've commented in the launchpad report.