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

2019-03-01 Thread fulvio ciriaco
Dear Daniel, On 3/1/19 8:48 PM, Daniel Kahn Gillmor wrote: > On Fri 2019-03-01 16:54:45 +0100, fulvio ciriaco wrote: >> I opened another session from VT with startx and >> exec dbus-launch awesome >> and the delay reappeared. >> >> The delay does not reappear with >> exec awesome > > ok, so it

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

2019-03-01 Thread Daniel Kahn Gillmor
On Fri 2019-03-01 16:54:45 +0100, fulvio ciriaco wrote: > I opened another session from VT with startx and > exec dbus-launch awesome > and the delay reappeared. > > The delay does not reappear with > exec awesome ok, so it works without "dbus-launch". in the scenario where you are *not* using

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

2019-03-01 Thread fulvio ciriaco
Dear Daniel, On 3/1/19 2:52 PM, Daniel Kahn Gillmor wrote: > [ privately to you, because your last message was just to me and not to > the BTS -- i'd prefer to have the conversation on the BTS though, so > it would help others in the future as well. I would be happy if you > wanted to post

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

2019-03-01 Thread Daniel Kahn Gillmor
On Thu 2019-02-28 16:13:27 +0100, fulvio ciriaco wrote: >> gpg-connect-agent 'get_confirmation abc123' /bye >> >> does it have a delay on the system in question? > > Yes, it has the same long delay. Ok, i think this identifies that the hang is happening in gpg-agent itself. >> do you have

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

2019-02-28 Thread 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

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

2019-02-26 Thread Daniel Kahn Gillmor
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.

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

2019-02-26 Thread fulvio ciriaco
Dear Daniel, the delay does not happen when getpin is called directly as in echo getpin | pinentry-gtk2 but it happens when for example I invoke pass show something 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

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

2019-02-25 Thread Daniel Kahn Gillmor
Control: tags 923068 + moreinfo Hi fc-- On Sat 2019-02-23 20:16:03 +0100, fc wrote: > When pinentry-gtk2 is started, the input window appears after more > than twenty seconds. For comparison pinentry-gnome3 and pinentry-qt > appear in less than two seconds for the same request. Can you take a