Please read the gpgv man page. Hint: Look at the first error message.

If you enter something on another desktop the pinentry should notice it and
return a cancel error. It all depends on the windows manager, though.

D132: 297_001-mips_gcc4.4.patch

Your logs show /dev/pts/7 and as I wrote in T1203:
other bug reports indicate that any /dev/pts/(single-digit) exposes the problem.

Might be related to T1203 (gpg-agent/pinentry does work on certain ttys
(/dev/pts/?)) so it should be checked if the number of tty has an influence
on the symptoms.

Testing pinentry Version: 0.8.0.svn231-0kk1
with window manager kwin from kdebase Version: 4:3.5.9.dfsg.1-6+lenny1.

That's a fair point. However it's just not there in glibc (at least I couldn't
find it). But if that's the only offending part the first two hunks could just
be skipped.

D131: 296_libgcrypt-1.4.5-ImplicitDSOLinking.patch

Does not look pretty.
I ask myself why glib does not implement its own printf functions to get rid of
such macros. I recently changed the gnupg code base to use the estream printf
functions which now allows us to use modern printf format specifiers. That is
much nicer than cluttering the code with casts or macros.

Applied. Thanks.

Hi Werner,
the G_* stuff is from GLIB/GTK+ so for a GTK+ object it's what somebody would
expect. If you want to stay close to the rest of the pinentry coding style I'm
or course fine with that.

No info received - assuming everything is fine now.

No, this proprietary software.

Tried several times in the past to rach Mike. The ACM membership expired.
Unfortunately lolo (the web maintainer) disapeared too. Thus we can't do much
right now.

Marcus, please decide whether we should apply them. Afaics, the options are not
the standard ones we use. The strange G_GSIZE_FORMAT macros look strange, we
better cast to int or use "%zd". Using the unused attribute to mark unused args
is not portable; better we access them (void)foo;

It turned out to be some work to reproduce the case. The length of the output
depends on the key and other factors. I created a test case which is now used
in armor.test which clearly shows this.

Note: The bug in the card's firmware has been fixed for some time now.

ping. Is that bug still relevant?

Solved. See T1214

Duplicate of T1214

Solved in a different way. See bug#1214

Duplicate of T1214

Fixed. Thanks.

David already fixed that in 1.4.
Now fixed for 2.0 too.

Marcus: I have an account on this machine. Let me know if I shall run a test
for you.

Changed the test framework again. Now it works on the buildfarm.

That seems to be a bad interaction between gpg-agent and keychain. AFAICS both
programs try to do the same: gpg-agent also implements the gpg-agent protocol.
It needs to be enabled, though.