Hi, I've run into this issue when my package manager updates gnupg without killing running gpg-agent daemons.
I think you have a previous (old version) gpg-agent daemon still running. You can see if that's the case by looking at the output of 'ps x'. I would recommend killing that daemon by using 'gpgconf --kill gpg-agent'. Your next invocation of a gpg command will launch a fresh daemon using the correct version. Chris On Thu, 11 Jul 2019 at 11:50, Matthias Herrmann via Gnupg-users < gnupg-users@gnupg.org> wrote: > Hello > > I've recently upgraded to Debian buster, and then upgraded gpg by > downloading and installing the new version 2.2.17. > Now, I get this warning: > > > gpg: WARNING: server 'gpg-agent' is older than us (2.2.12 < 2.2.17) > > $ gpg --version > gpg (GnuPG) 2.2.17 > libgcrypt 1.8.4 > > $ which gpg-agent > /usr/local/bin/gpg-agent > > $ /usr/local/bin/gpg-agent --version > gpg-agent (GnuPG) 2.2.17 > libgcrypt 1.8.4 > > $ gpgconf --list-dirs > sysconfdir:/usr/local/etc/gnupg > bindir:/usr/local/bin > libexecdir:/usr/local/libexec > libdir:/usr/local/lib/gnupg > datadir:/usr/local/share/gnupg > localedir:/usr/local/share/locale > socketdir:/run/user/1000/gnupg > > $ whereis gpg-agent > gpg-agent: /usr/bin/gpg-agent /usr/local/bin/gpg-agent > /usr/share/man/man1/gpg-agent.1.gz > > and: > $ /usr/bin/gpg-agent --version > gpg-agent (GnuPG) 2.2.12 > libgcrypt 1.8.4 > > $ echo $PATH > /usr/local/bin /usr/bin /bin /usr/local/games /usr/games > > I've even tried to add agent-program /usr/local/bin/gpg-agent to gpg.conf > > I don't know why the "wrong" agent gets started, can you please help me? > > -Hermi > > _______________________________________________ > Gnupg-users mailing list > Gnupg-users@gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-users >
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
