From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: bug#25328: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME Date: Fri, 20 Jan 2017 00:14:07 -0800 Message-ID: <87wpdqdu7k.fsf@gmail.com> References: <87a8ba44d5.fsf@gmail.com> <877f64r3qg.fsf@gnu.org> 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]:51889) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUULi-0007Dd-1k for bug-guix@gnu.org; Fri, 20 Jan 2017 03:15:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cUULe-0008JN-1N for bug-guix@gnu.org; Fri, 20 Jan 2017 03:15:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:37819) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cUULd-0008JJ-VA for bug-guix@gnu.org; Fri, 20 Jan 2017 03:15:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cUULd-0004HJ-Mv for bug-guix@gnu.org; Fri, 20 Jan 2017 03:15:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <877f64r3qg.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 09 Jan 2017 10:18:15 +0100") 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 25328@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, 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. ludo@gnu.org (Ludovic Court=C3=A8s) writes: > For the record, I=E2=80=99ve never experienced this problem (that=E2=80= =99s outside of > GNOME) with: For me, this problem doesn't happen outside of GNOME. > $ guix package -I '(gnupg|pinentry)' > pinentry 1.0.0 out /gnu/store/57dg2i4backl38bw4ipcsdg1b7df9j64-pinentry-1= .0.0 > gnupg 2.1.16 out /gnu/store/fz44xcp1iksikjvcc472bgsr9hs8ygkq-gnupg-2.1.16 I'm using these versions: $ guix package -I '(gnupg|pinentry)' gnupg 2.1.17 out /gnu/store/mcsi9rp06q0xxds4mwdgh1p16bifjxvk-gnupg-2.1.17 pinentry-gnome3 1.0.0 out /gnu/store/4kq8isyz7k8y64l7mjy90y4rjv7mh9x8-pin= entry-gnome3-1.0.0 The problem also occurred when using the "pinentry" package (instead of the "pinentry-gnome3" package): /gnu/store/b72r4rgr9irqy5zvb8i9hmrgrbb88ndf-pinentry-1.0.0 > 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. 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. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAliBxtAACgkQ3UCaFdgi Rp23cxAAplBsoKlZkTu3H5rlBerNyCyr2yPReJZ5vZNb7nyu0VaflkStCIyIIveG y+DWu5y5PVtgxS5k1i9y/eX0CQQBZo7kP1fdVBbz7cMqKSCQoj36EN2h2VITIkRe /8U7XvmBmj5XVeBPIopuAaUHTIbOi0wtioeLZFJ1IDAdSEpDaZSRwh707dZ5Xb70 u/kFK7dS+uXDEkYTcsxaEQC7O/j94QERYSUdE46CbmPPSLUxzh3S8PN3KoCCFoQB SIsU+VsAB6bns5gcNy97B1XymnEapsivnwes6VgztiGvI6FNX9E7Fx34TuIb62Gy bFoTBNL47TQZulpVVq+PAZXvK4QbeHemLTghcGzDw7yolWJs21ELCRYjx7OIVvP5 yKcJdBF0Esm6vmt8QPhh6XjbQ/tuGmCwTc2w/jlgNsYL6byBEriZrmmSDyC1u8CV XoImxaVEoCwzuf9WSG+PRXvtdz1rCPaf+IY3D9v71V7DUY1j3Y9ykZIfQRvfI7bY 7Rx9EVWVhnTMtW6aUZB65b8sOg5TFZh1DqVg/r9ud6IgJv5JASKTL/faUYB+mql2 olMkNnCaO0KbTIWCq/7zyIXdY/IkVxPbQor5eN/AIQtrNHDpMZ6THbVtIla7g2J/ axHio6TuQeh2JNFtLJFMINf5JqtozniLvH9APSu2+OgSJNJdSXQ= =6bNS -----END PGP SIGNATURE----- --=-=-=--