On 2025-05-14 Werner Koch via Gnupg-users <[email protected]> wrote: > On Wed, 14 May 2025 10:07, Andrew Gallagher said:
> > In what way does it interact badly? Is it worse than just a version > Systemd tries to start /usr/bin/gpg-agent as soon as another process > (e.g. /usr/local/bin/gpg) tries to connect to the gpg-agent socket. > Thus gpg will connect to a gpg-agent which is not the one installed > under /usr/local/bin (or whereever gnupg was installed). > Here is an untested hack to avoid this by using the gpgconf.ctl hack. [...] Hello, If the problem really is that gnupg 2.5 is installed alongside the distro gnupg 2.4 packages and the wrong agent (2.4) is started via systemd then the natural way to fix this is to mask the system user-units as described in /usr/share/doc/gpg-agent/README.Debian cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' _______________________________________________ Gnupg-users mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-users
