I don't understand... You succeeded in reproducing this and have an issue with
glibc?
If you do, have you opened some kind of bug report/thread to solve this?

Oops, I accidentially deleted iwm's message accompanying the attachment when
trying to remove my own duplicate. Sorry for that. Here is his original
message in full, you can also find it at:

Hi iwm,

Thanks for reporting this. There are a couple such issues where gnupg does not
issue an error message, and thus the operation will silently fail in GPGME as
well. In the past there used to be some heuristics in place which tried to
catch such situations, but they were causing other problems, so they were not
much of an improvement, and for 1.x I removed most of them.

A possible feature would be to tag requests with the name of the process (e.g.
mutt). However, this is hard to implement as we need to change it at many
places and extra arguments are required.

I gave it a shot and spent half a day on it. No way, I can't update the preview window without updating the actual text of the message. Chaning all messages to "This is a PGP/MIME message" is probably not a good idea. Code is in the new version 0.9.9 but deactivated.

Can't be done.

No example data received

Will be changed with 1.9. No fix in 1.4.

Won't be done because valgruind is a far better memory checker.

Recently switched to another db2man package. That might
help even on RedHat. Anyway closing this becuase we want to
move away from docbook.

I was wrong. The problem is that gcc does not define ARCH_PPC but our code relies on that.

The problem is described in the README file along with a
solution.

We hope to fix the Windows character set problems
(console/GUI) when revaming the internal translation
fucntions to a modernized versions.

This fix is part of 1.4.

Will be done (if still needed) in 1.9.

The code part of this has been handled. It is up to the
translators to do the rest. I'm marking this as suspended
(since it is not really closed).

Future versions won't use Docbook anymore so this is only an
issue for the current stable version.

Mailing-list manager URL is now a shared variable.

Maybe the fix must be retouched by LoLo.

Not easy to fix. Anyway with 1.9 we are going to change the
way secret keys are handled.

I send an e-mail to the reporter.

(en)All problems seems to be resolved up to date.
(es)Parece que todos los problemas ya han sido resueltos.

(es)No se detecta ningun problema con los manuales, ni
enlaces a gph/ .
(en)No problem detected about the manuals, nor links to gph/
.