emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#43035: closed (gpg-agent can't find pinentry with linux-libre-5.8.3)


From: GNU bug Tracking System
Subject: bug#43035: closed (gpg-agent can't find pinentry with linux-libre-5.8.3)
Date: Thu, 29 Sep 2022 06:27:02 +0000

Your message dated Thu, 29 Sep 2022 09:26:35 +0300
with message-id <YzU6m1wfLPuG97r6@3900XT>
and subject line Re: bug#43035: gpg-agent can't find pinentry with 
linux-libre-5.8.3
has caused the debbugs.gnu.org bug report #43035,
regarding gpg-agent can't find pinentry with linux-libre-5.8.3
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
43035: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43035
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: gpg-agent can't find pinentry with linux-libre-5.8.3 Date: Tue, 25 Aug 2020 12:45:45 +0300
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.

I added and removed the qemu-binfmt-service-type before the first
failure with 5.8 and after 5.7 worked. I've attached my os config, and
here's a link¹ to the repo.

(ins)efraim@E5400 ~$ guix describe
Generation 58   Aug 24 2020 23:35:45    (current)
  guix c88bccc
    repository URL: https://git.savannah.gnu.org/git/guix.git
    commit: c88bccc14e29fceb0ac2b139cb5c73546bcee352

¹ 
https://gitlab.com/Efraim/guix-config/-/tree/25470123d5a87c064f52ec4e0d939928bd22500c


-- 
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: E5400_config.scm
Description: Text document

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: bug#43035: gpg-agent can't find pinentry with linux-libre-5.8.3 Date: Thu, 29 Sep 2022 09:26:35 +0300
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: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]