Given that 2.1 will remove the helpers, I doubt that it makes sense to
put a lot of work into a new detection feature. What do you think of
this change:

• a/configure.ac

+++ b/configure.ac
@@ -157,8 +157,9 @@ if test -z "$GPG"; then
fi

dnl Find the keyserver plugins. Assume that gpgkeys_ldap is always available
-AC_PATH_PROG(GPGKEYS_LDAP, gpgkeys_ldap, [${libexecdir}/gnupg/gpgkeys_ldap],

• [$PATH:/usr/libexec/gnupg/:/usr/lib/gnupg/])

+AC_PATH_PROGS(GPGKEYS_LDAP, gpg2keys_ldap gpgkeys_ldap,
+ [${libexecdir}/gnupg/gpg2keys_ldap],
+ [$PATH:/usr/libexec/gnupg:/usr/lib/gnupg2:/usr/lib/gnupg])
KEYSERVER_HELPERS_DIR=dirname $GPGKEYS_LDAP
if test -z "$KEYSERVER_HELPERS_DIR"; then

        AC_MSG_ERROR([[

That is we check for gpg2keys_ldap first and also put the Debian
directory into the PATH.

My fix is for gpa (44b6bdf6) and gpgme (9f081da7).

It would be possible to do fix this only in GPA but the fix in gpgme makes gpgme
also more robust.

Applied to master (fb738b2). Thanks.

Doesn't occur in 0.9.2. Closing as 'resolved' myself.

Make sure that you paste a complete message. Use the command line if in doubt.
This is very likely a user error; ask on gnupg-users at gnupg.org for help

after pasting to clipboard i hit decrypt button but get the error message-
"General Error
This is probably a bug in GPA
GPA will now try to recover from this error".
nothing happens,gpa doesnt recover.
any suggestions please?
i am using it with web based hushmail running windows xp home

There is no version 2.1 of GPA.
Please tell us more details.

Fixed in commit 1ce38d7

Stored files can be in any encoding, as they are not displayed, so
interpretation is up to the user. But for a displayed string, the encoding matters.

Seems to be fixed in gpg4win 2.1.0

A better way to fix this is by looking at the output of gpgconf. Should not be
too hard to fix.

Sorry, without a detailed derror escription we can't help you. There are a
couple of known problems but gpg4win 1.1 is in any case not anymore under active
development.

No info received - assuming everything is fine now.

According to T1157 changing the locale does not help.

We need more input to figure out the problems. Please continue at issue#1125;
closing this one.

Duplicate of T1125

According to the error message this seems to be well and the message is probably
the result of a test for an valid UTF-8 char, but the stored file was creadted
from the same copy step via a second paste in the same step.

The content probably contains umlauts or accented characters for example in the
comment line or the text before the BEGIN PGP lines. We currently require the
clipboard to have valid utf-8 (or ascii) characters.

I have not tried with differnt volumes, but the current gpg4win release works
fine with regards to admin and normal user. Harry, can you please test if this
is still an issue, or if you have moved on from Windows 2000, I will just close
the report.

Applied (rev 1024). Thanks.

D117: 269_diff

Please find a minor patch attached. It fixes the formatting of the headline
(command should be all-uppercase). It further introduces a few formatting
requests (e.g. don't hyphenate the filename or the reference to gtk-options.

Thanks. Commited to the SVN -r 1023.

After talking to Arthur, the author of the manual page, the manual page is
provided under the GNU General Public license version 2 or (at your option) any
later version.

It was a problem with the gpgme Debian package:

D107: 253_typo_adresses.diff

There is further an "it's" which must be "its". Patch attached.

D108: 252_its_typo.diff

Duplicate of T1125

See T1125.

There is no version 2.0 of GPA, I assume yo mean the version included in gpg4win
2.0.

Sorry, we can't read doc files on our development machines.
If that inhcludes a screenshot, it won't help too much, we need a more detailed
error description. See "Add debug information" at
http://www.gpg4win.org/reporting-bugs.html .