[pkg-gnupg-maint] Bug#834633: gpg: signing failed / agent_genkey failed: Operation cancelled

[linus.luessing at c0d3.blue]

Package: gnupg
Version: 2.1.14-5
Severity: important

Hi,

Since recently (the update from gnupg 2.1.11-7 to 2.1.14-5 yesterday?)
I'm unable to use gnupg. I'm unable to decrypt mails in mutt now, and on
the console, key generation or file signing fails like this:

~~~~~
userA$ LANG=EN gpg -v -v --gen-key
gpg (GnuPG) 2.1.14; Copyright (C) 2016 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Note: Use "gpg --full-gen-key" for a full featured key generation dialog.

GnuPG needs to construct a user ID to identify your key.

Real name: Max Mustermann
Email address: test at example.com
You selected this USER-ID:
    "Max Mustermann <test at example.com>"

Change (N)ame, (E)mail, or (O)kay/(Q)uit? O
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: agent_genkey failed: Operation cancelled
Key generation failed: Operation cancelled
~~~~~

~~~~~
userB$ cd /tmp/; echo testfile > testfile.txt && LANG=EN gpg -v --sign -b testfile.txt
gpg: using pgp trust model
gpg: using "00B7A52F" as default secret key for signing
gpg: writing to 'testfile.txt.sig'
gpg: signing failed: Operation cancelled
gpg: signing failed: Operation cancelled
~~~~~

As I read something about systemd integration in the other tickets, I
checked "systemctl list-units" and there are no failed ones. Rebooting
the system did not help either.

Also trying to start a gpg-agent.service (not sure whether this is
relevant) fails:

~~~~~
userA$ LANG=EN systemctl --user enable gpg-agent; LANG=EN systemctl --user start gpg-agent
Failed to connect to bus: No such file or directory
Failed to connect to bus: No such file or director
~~~~~

However, after invoking --sign or --gen-key, a gpg-agent is running:

~~~~~
ps -Af |grep gpg-agent | grep -v grep
userA    4370     1  0 18:36 ?        00:00:00 gpg-agent --homedir <USERAHOME>/.gnupg --use-standard-socket --daemon
userB    6127     1  0 18:39 ?        00:00:00 gpg-agent --homedir <USERBHOME>/.gnupg --use-standard-socket --daemon
~~~~~

Please let me know if you need any further information. Thanks :-).

Regards, Linus


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 4.2.3-00234-g11acd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnupg depends on:
ii  gnupg-agent    2.1.14-5
ii  libassuan0     2.4.3-1
ii  libbz2-1.0     1.0.6-8
ii  libc6          2.23-4
ii  libgcrypt20    1.7.2-2
ii  libgpg-error0  1.24-1
ii  libksba8       1.3.4-4
ii  libreadline6   6.3-8+b4
ii  libsqlite3-0   3.14.1-1
ii  zlib1g         1:1.2.8.dfsg-2+b1

Versions of packages gnupg recommends:
ii  dirmngr     2.1.14-5
ii  gnupg-l10n  2.1.14-5

Versions of packages gnupg suggests:
pn  parcimonie  <none>
pn  xloadimage  <none>

-- no debconf information