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


-- 
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