Package: gnupg-agent Version: 2.0.18-1 Severity: normal Dear Maintainer,
I'm having trouble making gnupg-agent work with pinentry when ibus is around. The problem happens when sending a signed email with kmail. When I hit the Send button it should ask me the password but it actually tells me "Signing failed: Bad passphrase". The bug looks pretty similar to the one discribed on RedHat bugzilla [0]. [0] https://bugzilla.redhat.com/show_bug.cgi?id=228953 I made a try earlier and unsetting XMODIFIERS, QT_IM_MODULE and GTK_IM_MODULE did work but I can't make it work now. Maybe gnupg-agent or ibus need to be killed before unsetting these variable. However, this bug seems to have been fixed by upstream [1]. I checked this Debian package and, without surprise considering the date of the patch, it contains the mentionned code. [1] http://lists.gnupg.org/pipermail/gnupg-devel/2009-July/025222.html I have no clue what could be the problem but I'll run whatever test you need to solve this issue. One way of seeing the problem is to run: gpg-connect-agent "GET_PASSPHRASE gpg:foo foo bar baz" /bye Sometime I can see the pinentry window appear and disappear immediately. This is probably what makes kmail say the passphrase is incorrect, like if I was sending a return immediately. Best regards. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnupg-agent depends on: ii libassuan0 2.0.2-1 ii libc6 2.13-21 ii libgcrypt11 1.5.0-3 ii libgpg-error0 1.10-1 ii libpth20 2.0.7-16 ii libreadline6 6.2-4 ii pinentry-qt4 [pinentry] 0.8.1-1 Versions of packages gnupg-agent recommends: ii gnupg 1.4.11-3 ii gnupg2 2.0.18-1 ii gpgsm 2.0.18-1 gnupg-agent suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
