On Hans-Christoph wrote:
> 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:

for future reference, you should also see those error messages in:

     journalctl --user-unit dirmngr

and, it's not recommended to delete the sockets in question directly;
they are managed by your per-user systemd instance, so if you really do
want the socket to go away, you probably want to do soemthing like:

     systemctl --user stop dirmngr.socket



Reply via email to