From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 25328@debbugs.gnu.org
Subject: bug#25328: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME
Date: Sat, 21 Jan 2017 02:38:28 -0800 [thread overview]
Message-ID: <8737gc66l7.fsf@gmail.com> (raw)
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")
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
ludo@gnu.org (Ludovic Courtès) 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’t 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 “hack” I was referring to is probably just pinentry-gnome3.
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
> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791379>. 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.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-01-21 10:39 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
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 [this message]
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=8737gc66l7.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=25328@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).