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: Sat, 21 Jan 2017 02:38:28 -0800 Message-ID: <8737gc66l7.fsf@gmail.com> References: <87a8ba44d5.fsf@gmail.com> <877f64r3qg.fsf@gnu.org> <87wpdqdu7k.fsf@gmail.com> <878tq5ewi4.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]:54936) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUt4d-0007mv-Lk for bug-guix@gnu.org; Sat, 21 Jan 2017 05:39:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cUt4Y-0003hT-Ok for bug-guix@gnu.org; Sat, 21 Jan 2017 05:39:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:38687) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cUt4Y-0003hP-Le for bug-guix@gnu.org; Sat, 21 Jan 2017 05:39:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cUt4Y-0002gk-Ei for bug-guix@gnu.org; Sat, 21 Jan 2017 05:39:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <878tq5ewi4.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 20 Jan 2017 13:39: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 ludo@gnu.org (Ludovic Court=C3=A8s) writes: > 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. I've sent an email to gnupg-devel@gnupg.org asking for help. I'll update this bug report when I have more to report. > The =E2=80=9Chack=E2=80=9D I was referring to is probably just pinentry-g= nome3. I see. >> 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. :-) Weird. I'm not sure how to approach bugs like this. I could strace in the dark and hope to see something that shows me the light, but hopefully the gnupg email list will know better how to troubleshoot it. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAliDOiUACgkQ3UCaFdgi Rp1/XA/9HCJYfMZzxKkb7hK4HL9nu5GBJsh/gwBnVuyO62Yn3IY3CBJRbbKUUoeg dZvP7dzS1E02PQlzkAbjEPN6sGgsFksqANEZOfb+UGzi2YEn8DqzWOFYoy7RE9JX sarIS2fGdTe2dF3WxuOS6FF7U4HeMrmfF5cgDudMI8u1xsbMeGRD6uxmGzK6p0JK bRM/8HkZRM1QRpxZ0OjeHNtFO8/6xnc0xt56r/Hbxj+zDDEEQtqlfzpS5PhEOogS 4c7hSYIpSRSRFqTgZM/8FgBJ+BXsP3h1le9/yH0cCCcw6NTgKfYaHLmafSkKgvXF w4syiOfcTUOPVwwfsM1TYszvFioYZKi0OR/t9h/PBfAhx/kmfG2oSe9Lf3Z3npJf SWCVMA7q+iC4rxb83+J0nBA03UihDgZkPgOdkuAGjVpQ5QVu6iOe8L8ONha3GIxv guV9EGU+02e/zjaQeLA5XHoLfyEN+JPrc1UvXvjscYYa8N3NTcg0aShejhoBgx32 JZlfVg604P5lXgCz7iEpikw+y9NNPIa9Sed9VjVmFL+sOgS5pu47jaf4InR2K+m/ WJ3a6Xa8JN7d2KzsRxns/AEvVY0gZa94J47WfNB9V9hzQy2XbIxVDLVzyWNfKKj8 12EuRz6wyP4yrIiArSWk8TKsTdkx+T8pR/peoAsyAOCv2lc9Hog= =9Sg0 -----END PGP SIGNATURE----- --=-=-=--