From: Leo Famulari <leo@famulari.name>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 25328@debbugs.gnu.org
Subject: bug#25328: pinentry-gtk-2 fails after upgrade to 1.0.0: "Operation cancelled"
Date: Sun, 7 May 2017 19:33:59 -0400 [thread overview]
Message-ID: <20170507233359.GA20778@jasmine> (raw)
In-Reply-To: <42903767.AEQAKKXjfu8AAAAAAAAAAAO8QtMAAAACwQwAAAAAAAW9WABZD5yp@mailjet.com>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
On Mon, May 08, 2017 at 03:45:40AM +0530, Arun Isaac wrote:
> >> Since upgrading pinentry-gtk-2 from 0.9.7 to 1.0.0, I've noticed some
> >> strange behavior. Whenever I try to do something that requires access
> >> to my secret key, no window appears, and I get an error like the
> >> following:
> >>
> >> $ gpg --sign /tmp/message
> >> gpg: signing failed: Operation cancelled
> >> gpg: signing failed: Operation cancelled
>
> I am experiencing the exact same problem with pinentry-gtk-2 in exwm
> (Emacs X Window Manager). The pinentry window seems to get closed
> immediately after it appears. I thought that this was some bug in
> exwm. But, now that you mention this, maybe something's wrong with
> pinentry-gtk-2.
Chiming in to say that Guix's pinentry-gtk-2 works fine for me on Debian
unstable.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-07 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877f5o6e1d.fsf@gmail.com>
2017-05-07 20:50 ` bug#25328: pinentry-gtk-2 fails after upgrade to 1.0.0: "Operation cancelled" Chris Marusich
2017-05-07 22:15 ` Arun Isaac
2017-05-07 23:33 ` Leo Famulari [this message]
2017-05-10 7:46 ` Chris Marusich
2017-05-10 8:00 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170507233359.GA20778@jasmine \
--to=leo@famulari.name \
--cc=25328@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.