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: Mon, 09 Jan 2017 10:18:15 +0100
Message-ID: <877f64r3qg.fsf@gnu.org>
References: <87a8ba44d5.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53369)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1cQW6d-00044e-Me
	for bug-guix@gnu.org; Mon, 09 Jan 2017 04:19:08 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1cQW6Y-0002jt-OT
	for bug-guix@gnu.org; Mon, 09 Jan 2017 04:19:07 -0500
Received: from debbugs.gnu.org ([208.118.235.43]:60217)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1cQW6Y-0002jp-L7
	for bug-guix@gnu.org; Mon, 09 Jan 2017 04:19:02 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1cQW6Y-0001hF-FF
	for bug-guix@gnu.org; Mon, 09 Jan 2017 04:19:02 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.25328.B25328.14839535086477@debbugs.gnu.org>
In-Reply-To: <87a8ba44d5.fsf@gmail.com> (Chris Marusich's message of "Sun, 01
	Jan 2017 17:50:30 -0800")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 25328@debbugs.gnu.org

Hi Chris,

Chris Marusich <cmmarusich@gmail.com> skribis:

> Since upgrading pinentry from 0.9.7 to 1.0.0, I've noticed some strange
> behavior.  In GNOME only, when gpg tries to access my secret key, the
> attempt fails without prompting me for my passphrase.  For example, it
> fails like this:
>
> [0] marusich@garuda:~
> $ echo hello > /tmp/message
> [0] marusich@garuda:~
> $ gpg --sign /tmp/message=20
> gpg: signing failed: Operation cancelled
> gpg: signing failed: Operation cancelled
> [2] marusich@garuda:~
> $=20

For the record, I=E2=80=99ve never experienced this problem (that=E2=80=99s=
 outside of
GNOME) with:

--8<---------------cut here---------------start------------->8---
$ 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
--8<---------------cut here---------------end--------------->8---

ISTR that GNOME has a hack to force its own Pinentry tool.  Could it be
what=E2=80=99s at fault?

Thanks,
Ludo=E2=80=99.