From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#25328: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME Date: Fri, 20 Jan 2017 13:39:15 +0100 Message-ID: <878tq5ewi4.fsf@gnu.org> References: <87a8ba44d5.fsf@gmail.com> <877f64r3qg.fsf@gnu.org> <87wpdqdu7k.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43138) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUYUA-0004Cw-M9 for bug-guix@gnu.org; Fri, 20 Jan 2017 07:40:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cUYU6-0004Ap-MG for bug-guix@gnu.org; Fri, 20 Jan 2017 07:40:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:37889) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cUYU6-0004Al-In for bug-guix@gnu.org; Fri, 20 Jan 2017 07:40:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cUYU6-0003p0-Cl for bug-guix@gnu.org; Fri, 20 Jan 2017 07:40:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87wpdqdu7k.fsf@gmail.com> (Chris Marusich's message of "Fri, 20 Jan 2017 00:14:07 -0800") 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: Chris Marusich Cc: 25328@debbugs.gnu.org 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.