GNU bug report logs - #25328
gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME

Previous Next

Full log

Message #8 received at 25328 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich <at> gmail.com>
Cc: 25328 <at> debbugs.gnu.org
Subject: Re: bug#25328: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME
Date: Mon, 09 Jan 2017 10:18:15 +0100

Hi Chris,

Chris Marusich <cmmarusich <at> 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 <at> garuda:~
> $ echo hello > /tmp/message
> [0] marusich <at> garuda:~
> $ gpg --sign /tmp/message 
> gpg: signing failed: Operation cancelled
> gpg: signing failed: Operation cancelled
> [2] marusich <at> garuda:~
> $ 

For the record, I’ve never experienced this problem (that’s 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’s at fault?

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.