From debbugs-submit-bounces@debbugs.gnu.org Fri Jan 20 07:39:30 2017 Received: (at 25328) by debbugs.gnu.org; 20 Jan 2017 12:39:30 +0000 Received: from localhost ([127.0.0.1]:36087 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUYTa-0003o7-4N for submit@debbugs.gnu.org; Fri, 20 Jan 2017 07:39:30 -0500 Received: from eggs.gnu.org ([208.118.235.92]:51859) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUYTX-0003nt-4I for 25328@debbugs.gnu.org; Fri, 20 Jan 2017 07:39:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cUYTO-0003kU-RN for 25328@debbugs.gnu.org; Fri, 20 Jan 2017 07:39:21 -0500 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_50,RP_MATCHES_RCVD autolearn=disabled version=3.3.2 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:37177) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUYTO-0003kO-NW; Fri, 20 Jan 2017 07:39:18 -0500 Received: from [193.50.110.143] (port=39386 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cUYTO-0002hM-1s; Fri, 20 Jan 2017 07:39:18 -0500 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) To: Chris Marusich Subject: Re: bug#25328: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME References: <87a8ba44d5.fsf@gmail.com> <877f64r3qg.fsf@gnu.org> <87wpdqdu7k.fsf@gmail.com> X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 1 =?utf-8?Q?Pluvi=C3=B4se?= an 225 de la =?utf-8?Q?R?= =?utf-8?Q?=C3=A9volution?= X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-unknown-linux-gnu Date: Fri, 20 Jan 2017 13:39:15 +0100 In-Reply-To: <87wpdqdu7k.fsf@gmail.com> (Chris Marusich's message of "Fri, 20 Jan 2017 00:14:07 -0800") Message-ID: <878tq5ewi4.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -8.2 (--------) X-Debbugs-Envelope-To: 25328 Cc: 25328@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -8.2 (--------) Hi Chris, Chris Marusich skribis: > Previously, I wrote: > >> In GNOME, this issue DOES occur regardless of which "pinentry" program >> I specify in my ~/.gnupg/gpg-agent.conf file (the same issue occurs >> with pinentry, pinentry-curses, pinentry-gtk-2, and pinentry-tty). > > I don't think this is actually true. I believe I made an error when > testing the different pinentry programs. I believe I forgot to restart > the gpg-agent, which would explain why simply changing the contents of > the gpg-agent.conf file did not seem to fix the issue. > > I did another test just now. I tried changing the contents of the > gpg-agent.conf file, and I made sure to kill the gpg-agent process after > each change, so that gpg-agent would reload the file for sure. When I > did this, I found that only pinentry-gtk-2 exhibits this issue (note > that pinentry is a symlink to pinentry-gtk-2). In particular, > pinentry-curses, pinentry-tty, and pinentry-gnome3 all worked for me. > > Is anyone able to reproduce the issue using pinentry-gtk-2? The > following steps should 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. > > * Try to sign a message, e.g.: > > echo hello > /tmp/message > gpg --sign /tmp/message > > You should get the error very frequently. Could you report these steps upstream? That does not seem to be Guix-specific, though I suppose other distros probably install pinentry-gnome3 automatically when you install GNOME, such that the problem doesn=E2=80=99t show up. >> ISTR that GNOME has a hack to force its own Pinentry tool. Could it be >> what=E2=80=99s at fault? > > Where can I find more info about this hack? I did some Internet > searches, but I couldn't find anything specific. The =E2=80=9Chack=E2=80=9D I was referring to is probably just pinentry-gno= me3. > This bug is no longer blocking me, since I can use pinentry-gnome3, but > I'm still concerned about the fact that pinentry-gtk-2 fails very > frequently, even though it didn't on the previous version. It seems like bad interaction between pinentry-gtk2 and GNOME. On this topic, I found . Strangely, that bug discusses the opposite problem. :-) Ludo=E2=80=99.