Bug#796564: [pkg-gnupg-maint] Bug#796564: Bug#796564: Upgrade to gpg2.1 breaks enigmail

2015-08-30 Thread Michael Biebl
Hi! Am 31.08.2015 um 01:31 schrieb Daniel Kahn Gillmor: > please see https://bugs.debian.org/794627 -- is this the same issue? Yep, definitely looks like it, pinentry-gtk2 works fine, the gnome3 or qt4 one doesn't. I have to say that I installed enigmail via addons.mozilla.org, so I don't have t

Bug#796564: [pkg-gnupg-maint] Bug#796564: Bug#796564: Upgrade to gpg2.1 breaks enigmail

2015-08-30 Thread Daniel Kahn Gillmor
On Tue 2015-08-25 15:32:03 -0400, Werner Koch wrote: > On Tue, 25 Aug 2015 18:52, bi...@debian.org said: > >> Hm, that's strange. I did get the GNOME3 pinentry dialogs when using >> TB/Icedove + enigmail with gpg2.0. So for me the current behaviour is a > > Probably because gpg-agent has been star

Bug#796564: [pkg-gnupg-maint] Bug#796564: Upgrade to gpg2.1 breaks enigmail

2015-08-25 Thread Werner Koch
On Tue, 25 Aug 2015 18:52, bi...@debian.org said: > Hm, that's strange. I did get the GNOME3 pinentry dialogs when using > TB/Icedove + enigmail with gpg2.0. So for me the current behaviour is a Probably because gpg-agent has been started withn the right dbus session information. With 2.1 gpg-ag

Bug#796564: [pkg-gnupg-maint] Bug#796564: Upgrade to gpg2.1 breaks enigmail

2015-08-25 Thread Michael Biebl
Am 24.08.2015 um 14:56 schrieb Werner Koch: > On Mon, 24 Aug 2015 12:02, bi...@debian.org said: > >> Is this a bug in enigmail then? Any ideas why this worked with gpg2.0? > > pinentry-gnome requires some extra information for proper working thus > Enigmail needs to be changed as well. IIRC, 2.0

Bug#796564: [pkg-gnupg-maint] Bug#796564: Upgrade to gpg2.1 breaks enigmail

2015-08-24 Thread Werner Koch
On Mon, 24 Aug 2015 12:02, bi...@debian.org said: > Is this a bug in enigmail then? Any ideas why this worked with gpg2.0? pinentry-gnome requires some extra information for proper working thus Enigmail needs to be changed as well. IIRC, 2.0 does not yet support pinentry-gnome. Salam-Shalom,

Bug#796564: [pkg-gnupg-maint] Bug#796564: Upgrade to gpg2.1 breaks enigmail

2015-08-24 Thread Michael Biebl
Am 23.08.2015 um 17:21 schrieb Werner Koch: > On Sat, 22 Aug 2015 18:21, bi...@debian.org said: > >> since the upgrade from gpg 2.0 to 2.1, enigmail no longer works >> properly. I use enigmail 1.8.2 which defaults to /usr/bin/gpg2. > > IIRC, Enigmail resets the environment when calling gpg and th

Bug#796564: [pkg-gnupg-maint] Bug#796564: Upgrade to gpg2.1 breaks enigmail

2015-08-23 Thread Werner Koch
On Sat, 22 Aug 2015 18:21, bi...@debian.org said: > since the upgrade from gpg 2.0 to 2.1, enigmail no longer works > properly. I use enigmail 1.8.2 which defaults to /usr/bin/gpg2. IIRC, Enigmail resets the environment when calling gpg and thus Pinentry does not get the dbus session info. As a

Bug#796564: Upgrade to gpg2.1 breaks enigmail

2015-08-22 Thread Michael Biebl
Package: gnupg2 Version: 2.1.7-2 Severity: important Hi, since the upgrade from gpg 2.0 to 2.1, enigmail no longer works properly. I use enigmail 1.8.2 which defaults to /usr/bin/gpg2. It no longer asks me to unlock my key when trying to sign emails but simply fails. I use GNOME and pinentry-gn