They exists but give kind of syntax errors. In the meantime I closed the gpgv.exe console (annoying on your primary workhorse) so I would probably have to check how these commands behave when the gpgv.exe pops up next time.
C:\>gpgconf --query-swdb usage: gpgconf --query-swdb NAME [VERSION] C:\>gpg-connect-agent --dirmngr 'loadswdb --force' /bye gpg-connect-agent: Hinweis: `--force'' wird nicht als Option betrachtet ERR 167772435 Unbekanntes IPC Kommando <Dirmngr> ERR 167772435 Unbekanntes IPC Kommando <Dirmngr> ---- p≡p Security SA / Andy Weber / [email protected] PGP: 6C43 6A16 8523 0758 D601 91E4 912A BD60 8814 9C3C On 20.04.2018 02:59, Daniel Kahn Gillmor wrote: > On Thu 2018-04-19 23:54:40 +0200, Andy Weber wrote: >> The process seems to be spawned by dirmngr.exe, ptree looks like this: >> >> + "C:\Program Files (x86)\GnuPG\bin\dirmngr.exe" --daemon --homedir >> C:/Users/<User>/AppData/Roaming/gnupg >> + dirmngr.exe (Suspended and fails to resume) >> + "C:\Program Files (x86)\GnuPG\bin\gpgv.exe" >> --enable-special-filenames --status-fd=2 --keyring "C:\Program Files >> (x86)\GnuPG\share\gnupg\distsigkey.gpg" -- -&1072 - >> + \??\C:\WINDOWS\system32\conhost.exe 0x4 > if it's dirmngr invoking gpgv, then it's likely being triggered by > dirmngr's attempt to check that the latest version of gpg is available. > > Can you run the following commands from cmd.exe successfully? > > gpgconf --query-swdb > gpg-connect-agent --dirmngr 'loadswdb --force' /bye > > that might help you to debug the problem a bit more directly than > dealing with enigmail in the loop. > > --dkg
0x912ABD6088149C3C.asc
Description: application/pgp-keys
_______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
