Bug 459042 – app-crypt/pinentry - pinentry-gtk uses 100% CPU when trying to fall back to a terminal which isn't available

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Jan Matějka (RETIRED) 2013-02-24 17:34:16 UTC]

Here is described the same issue http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559936

Here is an explanation I got from upstream:
pinentry
tries to fall back to a terminal and this is not always accessible,
e.g. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559936

Best way would be to ensure that you always have an accessible
gpg-agent, i.e. started with your X session. Personally I often use
long-running screen sessions, for these I unset DISPLAY and start a
separate gpg-agent just for this session before starting screen, so
I can detach and re-attach and always have a working gpg-agent.

Reproducible: Always

[Comment 1 Alon Bar-Lev (RETIRED) 2013-03-02 22:04:27 UTC]

You gave the same reference twice, is that in purpose?

Was this reported upstream, is there is upstream bug#?

I don't see any commit on this matter[1], will be glad to apply whatever upstream applies.

[1] http://git.gnupg.org/cgi-bin/gitweb.cgi?p=pinentry.git;a=blob;f=pinentry/pinentry-curses.c;hb=HEAD#l812

[Comment 2 Jan Matějka (RETIRED) 2013-03-04 12:48:14 UTC]

(In reply to comment #1)
> You gave the same reference twice, is that in purpose?
yes, I haven't noticed the link is in the text I was about to paste.

> Was this reported upstream, is there is upstream bug#?

Upstream doesn't seem to have a working issue tracker for pinentry.

[Comment 3 Alon Bar-Lev (RETIRED) 2013-03-30 22:30:03 UTC]

(In reply to comment #2)
> (In reply to comment #1)
> > You gave the same reference twice, is that in purpose?
> yes, I haven't noticed the link is in the text I was about to paste.
> 
> > Was this reported upstream, is there is upstream bug#?
> 
> Upstream doesn't seem to have a working issue tracker for pinentry.

Yes they have[1]...


[1] https://bugs.g10code.com/gnupg/index

[Comment 4 Andreas Sturmlechner 2014-11-03 00:21:02 UTC]

This might be the solution? http://git.gnupg.org/cgi-bin/gitweb.cgi?p=pinentry.git;a=commit;h=3803fd15942f2f25108e400be6cd6faef791c8f7

[Comment 5 Alon Bar-Lev (RETIRED) 2014-11-03 00:25:29 UTC]

(In reply to Andreas Sturmlechner from comment #4)
> This might be the solution?
> http://git.gnupg.org/cgi-bin/gitweb.cgi?p=pinentry.git;a=commit;
> h=3803fd15942f2f25108e400be6cd6faef791c8f7

please check it out and see if it helps.

[Comment 6 Andreas Sturmlechner 2015-01-10 23:38:14 UTC]

Created attachment 393654 [details, diff]
pinentry-0.9.0.ebuild.diff

(In reply to Alon Bar-Lev from comment #5)
> please check it out and see if it helps.
Well, personally I've not seen this error, but trying the 100% testcase given in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559936#15 I was not able to reproduce it.

Running pinentry-0.9.0, attaching ebuild.

[Comment 7 Kristian Fiskerstrand (RETIRED) 2015-09-10 13:05:31 UTC]

We believe this issue is fixed in recent versions of pinentry. If this issue still persists, please re-open this bug with additional information based on the updated versions.