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 00:46:50 -0700 Message-ID: <8737cd5f2t.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]:54189) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d8MKw-00025O-L9 for bug-guix@gnu.org; Wed, 10 May 2017 03:47:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d8MKt-0004vB-G9 for bug-guix@gnu.org; Wed, 10 May 2017 03:47:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:60558) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d8MKt-0004v6-CL for bug-guix@gnu.org; Wed, 10 May 2017 03:47:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1d8MKs-0006kU-VR for bug-guix@gnu.org; Wed, 10 May 2017 03:47:02 -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: 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. Looks like I might need to be subscribed to gnupg-devel in order to post to it, so I've subscribed for this purpose. I'll update this bug report again if my message actually shows up in the gnupg-devel list. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlkSxWoACgkQ3UCaFdgi Rp3Xvg//ceRt0JzKveu6ycEbk5VOjFyWE2K7ufqIZLQw8iqQcATii9vQ5xyDkFJi VzqiyEgcF9Tw1fOKyKqVeqTIBrAYMNRS8ZsCZvOVzvYr+QN2C4dYggQfrkqyrXtj NStzgY/F4h1RpBI/pSFQOBsIriPcK+/xN3A65r6oD80D1dF7oQPPZxXUNXUEBnku o3hm/2PK+SrBCmxk9v9Nfauh1pVJkkXEbCTXTxoZe5ms3VXi18ej9TfGUKXwfwT1 YRVK+Kk0p3jw1z8p2Zsj7NoXRq+nqh08qiYl1d6pBU6k7rJ5ySgD9X+yclPjLDkT ZP1TX0eRJCwT0tRtphvV9z6iHMaStit0tCucV/1n2SWufPAFfjMmlzozsBK1P6x5 38tII1OKIYOaVBzNLklKBSN/+LzE8AOMv26dyP4A/fgN4rncvi0CwF7SkTZMVF4I SD1wQ9kmzepJMsawwqnQic3UEweP6vMR9JXpsNGzQkjZr+rbhngRdR7yLe/GCt8c eTxVCoxnDmugzm8jbhkpp3UY3CMeDX6sRe8bZ/T6zkWF6EwEHayy9mlYzt9uKLKS /QJqGS0PqeWmJ6ITJiPgirPFQE3WhOaW/FoFt1EyjqdqAlNlYJCQMJr34klCvHTZ /xcTIm7KcjC40Wb3bq7HsI3VuQjtbEqr8SG7vPnZyrqg4kfzlYc= =4trK -----END PGP SIGNATURE----- --=-=-=--