From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: bug#25328: pinentry-gtk-2 fails after upgrade to 1.0.0: "Operation cancelled" Date: Wed, 10 May 2017 01:00:29 -0700 Message-ID: <87shkd3zvm.fsf@gmail.com> References: <877f5o6e1d.fsf@gmail.com> <87tw4wtmq4.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57015) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d8MYV-0005SQ-Ji for bug-guix@gnu.org; Wed, 10 May 2017 04:01:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d8MYQ-0000Zm-N8 for bug-guix@gnu.org; Wed, 10 May 2017 04:01:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:60578) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d8MYQ-0000Zi-8x for bug-guix@gnu.org; Wed, 10 May 2017 04:01:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1d8MYP-00075V-S2 for bug-guix@gnu.org; Wed, 10 May 2017 04:01:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87tw4wtmq4.fsf@gmail.com> (Chris Marusich's message of "Sun, 07 May 2017 13:50:59 -0700") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: gnupg-devel@gnupg.org Cc: 25328@debbugs.gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Chris Marusich writes: > Chris Marusich writes: > >> Hi, >> >> Since upgrading pinentry-gtk-2 from 0.9.7 to 1.0.0, I've noticed some >> strange behavior. Whenever I try to do something that requires access >> to my secret key, no window appears, and I get an error like the >> following: >> >> $ gpg --sign /tmp/message=20 >> gpg: signing failed: Operation cancelled >> gpg: signing failed: Operation cancelled >> $=20 >> >> Is this expected behavior with 1.0.0? >> >> This happens about 90% of the time. About 10% of the time, a pinentry >> window actually does pop up. When using version 0.9.7, a pinentry >> window popped up 100% of the time. I expected the behavior of 1.0.0 to >> be the same. >> >> My software versions are: >> >> * GuixSD 0.12.0 >> * GNOME 3 (GNOME shell 3.22.2) >> * gnupg 2.1.16 >> * pinentry-gtk-2 1.0.0 >> >> My ~/.gnupg/gpg-agent.conf file contains the following single line: >> >> pinentry-program /home/marusich/.guix-profile/bin/pinentry-gtk-2 >> >> When I change my gpg-agent.conf file to use pinentry-gnome3 , >> pinentry-curses, or pinentry-tty (and I kill gpg-agent to make sure it >> uses the modified file), the problem doesn't occur. >> >> When I keep pinentry-gtk-2 in my gpg-agent.conf file, and I log into an >> Xfce session, the problem doesn't occur. Likewise, when I log in via a >> virtual terminal (e.g. the kind you can get by pressing Control+Alt+F2), >> the problem doesn't occur. >> >> In other words, the problem only seems to occur when I use >> pinentry-gtk-2 as my pinentry-program, and I'm logged into a GNOME 3 >> session. The problem occurs regardless of what program I am running >> inside of that GNOME 3 session; for example, it happens in emacs when >> emacs tries to automatically decrypt files ending in ".gpg", too. >> >> Here's how to reproduce the issue: >> >> * Log into a GNOME session on (a recently updated) GuixSD. >> >> * In $HOME/.gnupg/gpg-agent.conf, set pinentry-program to >> pinentry-gtk-2, for example: >> >> pinentry-program /home/marusich/.guix-profile/bin/pinentry-gtk-2 >> >> * If the gpg-agent process is running, kill it to make sure it loads the >> new gpg-agent.conf. >> >> * Open up any terminal (GNOME terminal and emacs' "M-x term" will both >> reproduce the issue) to sign a message, e.g.: >> >> echo hello > /tmp/message >> gpg --sign /tmp/message >> >> You should get the error very frequently. > > Did anybody get this message? I sent it in January of 2017, but I can't > find it in the online archives, so I'm worried maybe it never got > delivered: > > https://lists.gnupg.org/pipermail/gnupg-devel/ > > This time, I've CC'd 25328@debbugs.gnu.org so that my email gets > delivered to at least one location for posterity. I can no longer reproduce this issue. I tried following the steps above on my current GuixSD system, and the problem does not occur. It seems like pinentry-gtk-2 works fine now, which is curious because the version is still 1.0.0. I don't know why it works now but didn't earlier. My emails never seem to have made it to the gnupg-devel list, but in this case I suppose it doesn't matter any more. I think we can resolve this bug report, unless someone else can reproduce the issue reliably. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlkSyJ0ACgkQ3UCaFdgi Rp08KQ//WDdZpv6h6rS4vvjLNSpPp1wSddx8U3F5ruzD8Cm6vnK3teFDFo0Eb1g4 m0q29hohqt4hkYLKi/c1qkItVwWug/QwU7PTH2bWOkAzW1wYYdRaB/Ck/COKf6Ed FQnmQydd4cF/x/Pvk15VkThgDLw+uO3D2McqY53jmaIPp6k/R+Vz1ifYsleNim6Y w2CA8zE7A7MIaX8IUzS3TRIy3Qi1XNhKsffoDE5+YiHoEH8HACqVx96EQ8O0aRJv xOuoVZuthTrM8gQhGeRV33uoE2XMreW3tl6Olmf74gRO4w8wtwetEV/+Hw6nw3lu bJzG8qg6HJB2LzDZD6pFBMaUtALSMX25rxiwurVKZKjKqQ92h+4aG0iWuPZa4rLP i+0X24pP7V7oj0RJNXJjv0oUyTkg598rPpHmXXIyIBxDhH2cmdnCHhhNpWFjUWpT llQ29LRVosOG+qgzMn8W059pi302B/6Frd5xlHX2rQ1FMxDwSSvXkCp2n28kJ3+w 6RRl/KN58CMYftubqBO6a4BCssvabDCBclO7XZTBpN4J6Q/47KU2W2D4xHW0dCIV d5KSSsBtcS2xHrhFk82/8/2mkh0Unhn4y0hmuEYePiHukfqmUFLJj/WQtKhT8YLe QI/1ArMnVlJswJIxXMCe6QnL7C+1/m16RkqYlPN1c0ucdyFIabs= =x8Ei -----END PGP SIGNATURE----- --=-=-=--