Processed: Re: Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Processing control commands: > clone -1 -2 Bug #850708 [pinentry-gtk2] pinentry-gtk-2 frequently fails to grab the pointer under fvwm Bug 850708 cloned as bug 851707 > retitle -2 pinentry-gtk-2 frequently fails to grab the keyboard under awesome Bug #851707 [pinentry-gtk2] pinentry-gtk-2

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Control: clone -1 -2 Control: retitle -2 pinentry-gtk-2 frequently fails to grab the keyboard under awesome <#secure method=pgpmime mode=sign> ❦ 17 janvier 2017 20:34 +0100, Vincent Lefevre  : >> ** (pinentry-gtk-2:21583): CRITICAL **: could not grab keyboard: not >>

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

On 2017-01-17 20:21:05 +0100, Vincent Bernat wrote: > Here is the output I get: > > OK Pleased to meet you > > ** (pinentry-gtk-2:21583): CRITICAL **: could not grab keyboard: not viewable > (3) > > ** (pinentry-gtk-2:21583): WARNING **: it took 4097 tries to grab the keyboard > > **

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

❦ 17 janvier 2017 12:13 +0100, Vincent Lefevre  : >> I have the same behaviour with awesome. My setup didn't change since >> quite some time but this behaviour is recent while neither awesome nor >> pinentry-gtk2 has been updated. I got the behavior immediately after >>

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

On 2017-01-17 10:19:50 +0100, Vincent Bernat wrote: > I have the same behaviour with awesome. My setup didn't change since > quite some time but this behaviour is recent while neither awesome nor > pinentry-gtk2 has been updated. I got the behavior immediately after > rebooting. Applying the patch

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

❦ 11 janvier 2017 01:47 -0500, Daniel Kahn Gillmor  : > On Tue 2017-01-10 20:58:16 -0500, Vincent Lefevre wrote: >> On 2017-01-10 18:26:57 -0500, Daniel Kahn Gillmor wrote: >>> what window manager are you using? >> >> fvwm > > hm, both Vincent and gi1242 are using fvwm.

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Control: tags -1 patch On 2017-01-11 11:45:07 +0100, Vincent Lefevre wrote: > In pinentry-gtk-2.c: > > do > err = gdk_pointer_grab (gtk_widget_get_window (win), > TRUE, 0 /* event mask */, > NULL /* confine to */, >

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

On 2017-01-11 11:00:39 +0100, Vincent Lefevre wrote: > So, the application may need to wait a little bit instead of failing > immediately (I suppose that the problem is more visible on multicore > machines). In pinentry-gtk-2.c: do err = gdk_pointer_grab (gtk_widget_get_window (win),

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Control: retitle -1 pinentry-gtk-2 frequently fails to grab the pointer under fvwm Control: tags -1 -unreproducible since it is reproducible with fvwm (now mentioned in the bug title) and the reason is clearly given in the fvwm(1) man page. On 2017-01-11 01:47:53 -0500, Daniel Kahn Gillmor

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

On 2017-01-11 01:47:53 -0500, Daniel Kahn Gillmor wrote: > hm, both Vincent and gi1242 are using fvwm. can you try installing > openbox or some other comparable minimalist window manager and let me > know whether you still see the same misbehavior? it sounds to me like > y'all might have hit on

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Control: retitle 850708 pinentry-gtk-2 frequently fails to grab the keyboard under fvwm Control: affects 850708 + fvwm On Tue 2017-01-10 20:58:16 -0500, Vincent Lefevre wrote: > On 2017-01-10 18:26:57 -0500, Daniel Kahn Gillmor wrote: >> what window manager are you using? > > fvwm hm, both

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Control: found -1 1.0.0-1 On 2017-01-10 18:26:57 -0500, Daniel Kahn Gillmor wrote: > On Mon 2017-01-09 22:08:09 -0500, Vincent Lefevre wrote: > > On 2017-01-09 18:00:14 -0500, Daniel Kahn Gillmor wrote: > >> what happens if you do: > >> > >> gpg-connect-agent 'get_passphrase cacheval123

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Control: reassign 850708 pinentry-gtk-2 On Mon 2017-01-09 22:08:09 -0500, Vincent Lefevre wrote: > On 2017-01-09 18:00:14 -0500, Daniel Kahn Gillmor wrote: >> what pinentry are you using? > > pinentry-gtk-2 > > No problems with pinentry-curses. I've reassigned this bug report to pinentry-gtk-2.

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Hi There, I think this is a bug with pinentry-gtk-2. Running it almost always results in the following warning: $ echo getpin | pinentry-gtk-2 OK Pleased to meet you ** (pinentry-gtk-2:28067): WARNING **: it took 32 tries to grab the keyboard D this is a test OK Sometimes

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

On 2017-01-09 18:00:14 -0500, Daniel Kahn Gillmor wrote: > On Mon 2017-01-09 10:02:20 -0500, Vincent Lefevre wrote: > > Since the latest upgrade: > > > > * When I open a .gpg file with Emacs: > > > > * With "gpg -d note.gpg", same errors: > > > > gpg: AES encrypted data > > gpg: cancelled by user

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Control: tags 850708 + moreinfo unreproducible Hi Vincent-- On Mon 2017-01-09 10:02:20 -0500, Vincent Lefevre wrote: > Since the latest upgrade: > > * When I open a .gpg file with Emacs: > > * With "gpg -d note.gpg", same errors: > > gpg: AES encrypted data > gpg: cancelled by user > gpg: