From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 25328@debbugs.gnu.org
Subject: bug#25328: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME
Date: Mon, 09 Jan 2017 10:18:15 +0100 [thread overview]
Message-ID: <877f64r3qg.fsf@gnu.org> (raw)
In-Reply-To: <87a8ba44d5.fsf@gmail.com> (Chris Marusich's message of "Sun, 01 Jan 2017 17:50:30 -0800")
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
> gpg: signing failed: Operation cancelled
> gpg: signing failed: Operation cancelled
> [2] marusich@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’.
next prev parent reply other threads:[~2017-01-09 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 1:50 bug#25328: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME Chris Marusich
2017-01-09 9:18 ` Ludovic Courtès [this message]
2017-01-20 8:14 ` Chris Marusich
2017-01-20 12:16 ` Daniel Pimentel
2017-01-20 12:39 ` Ludovic Courtès
2017-01-21 10:38 ` Chris Marusich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877f64r3qg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25328@debbugs.gnu.org \
--cc=cmmarusich@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).