gnupg 2.x spawns dirmngd daemon whenever using gpg
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnupg2 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1. lsb_release -rd
Description: Ubuntu Yakkety Yak (development branch)
Release: 16.10
2. apt-cache policy gnupg
gnupg:
Installed: 2.1.15-1ubuntu2
Candidate: 2.1.15-1ubuntu2
Version table:
*** 2.1.15-1ubuntu2 500
500 http://
100 /var/lib/
3. after gpg exits, there are no new daemons running
4. gpg-agent and dirmngr are running as daemons with open filehandles
# cat pstree_
systemd(
| `-{gmain}(111)
| `-{gmain}(121)
| `-{rs:main Q:Reg}(125)
| |-{snapd}(127)
| |-{snapd}(128)
| |-{snapd}(129)
| |-{snapd}(130)
| `-{snapd}(131)
root@gpgv2:~# cat lsof_gpg_
dirmngr 559 root 3u unix 0x0000000000000000 0t0 35823861 /tmp/tmpv9bs89h
ldap-reap 559 560 root 3u unix 0x0000000000000000 0t0 35823861 /tmp/tmpv9bs89h
This also breaks things that set a 'no damon policy' in invoke-rc.d as gpg spawns these daemons rather than creating dirmngr or gpg-agent as service units that could be socket activated.
One such error path is when using cloud-utils mount-image-
The easiest recreate is to:
sudo add-apt-repository -y ppa:<some ppa>
on a yakkety system.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnupg 2.1.15-1ubuntu2
ProcVersionSign
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Thu Sep 22 16:27:38 2016
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
SourcePackage: gnupg2
UpgradeStatus: No upgrade log present (probably fresh install)