[pkg-gnupg-maint] Bug#923068: Bug#923068: pinentry-gtk2 takes more than twenty seconds to appear

[fulvio ciriaco]

Dear Daniel,


On 2/27/19 8:16 AM, Daniel Kahn Gillmor wrote:
> Control: reassign 923068 gpg-agent 2.2.12-1
> 
> On Wed 2019-02-27 07:30:39 +0100, fulvio ciriaco wrote:
> 
>> the delay does not happen when getpin is called directly as in
>> echo getpin | pinentry-gtk2
> 
> ok, so that means that the issue isn't in pinentry itself.  It's
> probably in gpg-agent or elsewhere.
> 
> So the next diagnostic step is to get other things out of the loop, like
> gpg itself, and just try to debug the agent and how it interoperates
> with pinentry.
> 
> For example, this command should cause an immediate popup confirmation
> dialog box:
> 
>     gpg-connect-agent 'get_confirmation abc123' /bye
> 
> does it have a delay on the system in question?
> 

Yes, it has the same long delay.

>> I read the thread for bug 800032 you pointed me to and noticed that on another machine
>> I have there is no delay. I noticed that on the other machine, my wm awesome is launched
>> directly, on the machine where the delay happens it is called through:
>> exec dbus-launch awesome
>> so I guess dbus-launch has to do with the problem.
> 
> do you have dbus-user-session installed on both of these systems?  how
> does "exec dbus-launch awesome" itself get executed?  from a VT, or from
> some other automated process?
> 

I login through lightdm, it is the last line of my .xsession

Fulvio

>      --dkg
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnupg-maint/attachments/20190228/568b7dc1/attachment.sig>