Package: gnupg-agent Version: 2.1.11-6ubuntu2 Severity: normal Dear Maintainer,
I followed the instructions of Emacs 25's pinentry.el: ;; To use, add "allow-emacs-pinentry" to "~/.gnupg/gpg-agent.conf", ;; reload the configuration with "gpgconf --reload gpg-agent", and ;; start the server with M-x pinentry-start. and then I tried "gpg --decrypt ~/.authinfo.gpg" from a regular terminal (not inside Emacs). This gave me the confusing message "no secret key", where before it had worked just fine (with a gtk2 pinentry dialog asking for my password). Removing the "allow-emacs-pinentry" and doing "gpgconf --reload gpg-agent" makes regular "gpg --decrypt ~/.authinfo.gpg" work again. If Debian needs to remove Emacs pinentry support from gnupg, it should probably still have a better error message. However, from what I can read of https://bugs.gnupg.org/gnupg/issue2034 (where the reasons for removing Emacs support are given), all the arguments against support are taken care of: Bug-dependencies 2057 and 2059 are closed, while 2058 seems to have turned into feature request not needed for closing 2034. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100, 'xenial-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-38-generic (SMP w/2 CPU cores) Locale: LANG=nn_NO.UTF-8, LC_CTYPE=nn_NO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnupg-agent depends on: ii libassuan0 2.4.3-1 ii libc6 2.23-0ubuntu3 ii libgcrypt20 1.6.5-2ubuntu0.2 ii libgpg-error0 1.21-2ubuntu1 ii libnpth0 1.2-3 ii libreadline6 6.3-8ubuntu2 ii pinentry-gnome3 [pinentry] 0.9.7-3 ii pinentry-gtk2 [pinentry] 0.9.7-3 Versions of packages gnupg-agent recommends: ii gnupg 1.4.20-1ubuntu3.1 ii gnupg2 2.1.11-6ubuntu2 gnupg-agent suggests no packages. -- no debconf information