Your message dated Mon, 8 Apr 2019 12:50:22 +0200
with message-id <[email protected]>
and subject line Re: Bug#926636: Acknowledgement (gpg: connecting dirmngr at
'/run/user/1000/gnupg/S.dirmngr' failed: IPC connect call failed)
has caused the Debian Bug report #926636,
regarding gpg: connecting dirmngr at '/run/user/1000/gnupg/S.dirmngr' failed:
IPC connect call failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
926636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926636
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dirmngr
Version: 2.2.12-1
On a fresh install of buster from a week ago, dirmngr was working
before. Now when I try to do `gpg --recv-keys`, dirmngr fails:
$ gpg --recv-keys 00aa5556
gpg: connecting dirmngr at '/run/user/1000/gnupg/S.dirmngr' failed: IPC
connect call failed
gpg: keyserver receive failed: No dirmngr
/run/user/1000/gnupg/S.dirmngr existed so I deleted it. But I got the
same message. /run/user/1000/gnupg/S.dirmngr no longer exists, and does
not seem to have been recreated.
--- End Message ---
--- Begin Message ---
Well, its kind of a bug, but more of an error reporting bug. I had a
bad option in ~/.gnupg/dirmngr.conf from before I upgraded to buster.
Running `dirmngr` bare gave me useful error output:
$ dirmngr
dirmngr[16342]: /home/hans/.gnupg/dirmngr.conf:1: invalid option
--- End Message ---
