From: Efraim Flashner <efraim@flashner.co.il>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 43035-done@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: bug#43035: gpg-agent can't find pinentry with linux-libre-5.8.3
Date: Thu, 29 Sep 2022 09:26:35 +0300 [thread overview]
Message-ID: <YzU6m1wfLPuG97r6@3900XT> (raw)
In-Reply-To: <871qrvqb1d.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2097 bytes --]
On Wed, Sep 28, 2022 at 08:28:14PM -0400, Maxim Cournoyer wrote:
> Hi,
>
> Efraim Flashner <efraim@flashner.co.il> writes:
>
> > On Mon, Aug 31, 2020 at 03:33:34PM -0400, Leo Famulari wrote:
> >> 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.
> >
> > I have a new one with 'strace -fv' where it still didn't work. Then I
> > figured that maybe it was custom pinentry-efl so I removed that and
> > switched to pinentry-efl and that didn't work. Then I removed that and
> > installed pinentry-gnome3 and suddenly that worked. So it looks like
> > it's pinentry-efl specific
>
> Is it OK to close this issue then? The title is rather misleading! :-)
>
Sure. I'm not even really sure what it's about right now. I assume the
problem is fixed.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-09-29 6:42 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
2020-09-03 11:14 ` Efraim Flashner
2022-09-29 0:28 ` Maxim Cournoyer
2022-09-29 6:26 ` Efraim Flashner [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=YzU6m1wfLPuG97r6@3900XT \
--to=efraim@flashner.co.il \
--cc=43035-done@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=maxim.cournoyer@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).