From: Leo Famulari <leo@famulari.name>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 43035@debbugs.gnu.org
Subject: bug#43035: gpg-agent can't find pinentry with linux-libre-5.8.3
Date: Mon, 31 Aug 2020 15:33:34 -0400 [thread overview]
Message-ID: <20200831193334.GA14615@jasmine.lan> (raw)
In-Reply-To: <20200831192036.GA856@E5400>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
On Mon, Aug 31, 2020 at 10:20:36PM +0300, Efraim Flashner wrote:
> On Tue, Aug 25, 2020 at 04:14:59PM -0400, Leo Famulari wrote:
> > On Tue, Aug 25, 2020 at 12:45:45PM +0300, Efraim Flashner wrote:
> > > This bug report sounds absurd to me but I don't see anything else
> > > obvious that changed. I reconfigured with (kernel linux-libre) and the
> > > gpg-agent couldn't find any pinentry. I even tried killing gpg-agent and
> > > manually launching it and giving it the path to pinentry. I then changed
> > > to (kernel linux-libre-5.7) and used the same commit to reconfigure and
> > > gpg-agent started working as expected again.
> >
> > Weird! You should run gpg-agent with `strace -f` and see where it is
> > looking.
>
> I've attached the strace from gpg-agent when I tried to run 'gpg -s'
> ^C+d. I'm not really sure what it could be but it looks like I should
> boot back into the 5.8.5 kernel generation and strace some more
> processes.
Okay, I'm still stumped. Next time use `strace -fv`, so that it doesn't
abbreviate useful information.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-31 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 9:45 bug#43035: gpg-agent can't find pinentry with linux-libre-5.8.3 Efraim Flashner
2020-08-25 20:14 ` Leo Famulari
2020-08-31 19:20 ` Efraim Flashner
2020-08-31 19:33 ` Leo Famulari [this message]
2020-09-03 11:14 ` Efraim Flashner
2022-09-29 0:28 ` Maxim Cournoyer
2022-09-29 6:26 ` Efraim Flashner
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=20200831193334.GA14615@jasmine.lan \
--to=leo@famulari.name \
--cc=43035@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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).