Windows: Pinentry not starting for some
Closed, ResolvedPublic

Description

Moved out from T4123:

in I think a related scenario we are having the pinentry window not spawn at all, leading to "no pinentry" errors
Win 10 latest patches Mar 2019
Version 3.1.4-gpg4win-3.1.5
We've tried a few hacks including adding the .conf file to C:\Program Files (x86)\GnuPG\bin with

pinentry-program "C:\Program Files (x86)\Gpg4win\bin\pinentry-qt.exe"

C:\WINDOWS\system32>gpg --debug ipc -vK
gpg: reading options from 'C:/Users/nbriggs/AppData/Roaming/gnupg/gpg.conf'
gpg: enabled debug flags: ipc
gpg: using pgp trust model
gpg: DBG: chan_0x00000260 <- OK Pleased to meet you
gpg: DBG: connection to agent established
gpg: DBG: chan_0x00000260 -> RESET
gpg: DBG: chan_0x00000260 <- OK
gpg: DBG: chan_0x00000260 -> GETINFO version
gpg: DBG: chan_0x00000260 <- D 2.2.11
gpg: DBG: chan_0x00000260 <- OK
gpg: DBG: chan_0x00000260 -> OPTION allow-pinentry-notify
gpg: DBG: chan_0x00000260 <- OK
gpg: DBG: chan_0x00000260 -> OPTION agent-awareness=2.1.0
gpg: DBG: chan_0x00000260 <- OK
gpg: DBG: chan_0x00000260 -> HAVEKEY *KEY*
gpg: DBG: chan_0x00000260 <- OK
gpg: DBG: chan_0x00000260 -> KEYINFO *KEY*
gpg: DBG: chan_0x00000260 <- S KEYINFO *KEY* D - - 1 P - - -
gpg: DBG: chan_0x00000260 <- OK
gpg: DBG: chan_0x00000260 -> KEYINFO *KEY*
gpg: DBG: chan_0x00000260 <- S KEYINFO *KEY* D - - - P - - -
gpg: DBG: chan_0x00000260 <- OK
C:/Users/nbriggs/AppData/Roaming/gnupg/pubring.kbx


sec rsa2048 2019-03-25 [SC] [expires: 2021-03-25]


uid [ultimate] Nathan ***
ssb rsa2048 2019-03-25 [E] [expires: 2021-03-25]

gpg: DBG: chan_0x00000260 -> HAVEKEY *KEY*
gpg: DBG: chan_0x00000260 <- ERR 67108881 No secret key <GPG Agent>
gpg: DBG: chan_0x00000260 -> HAVEKEY *KEY*
gpg: DBG: chan_0x00000260 <- ERR 67108881 No secret key <GPG Agent>
gpg: DBG: chan_0x00000260 -> HAVEKEY *KEY*
gpg: DBG: chan_0x00000260 <- ERR 67108881 No secret key <GPG Agent>
gpg: secmem usage: 0/32768 bytes in 0 blocks

Is there anything more I can do, replicated it on 3 different machines

Details

Version
3.1.5
aheinecke triaged this task as Normal priority.Mar 26 2019, 12:18 PM

Could it be that you are running into: T4347 ? Maybe this will just be fixed for you then in the next version.

What happens if you start pinentry-qt.exe directly and enter "getpin" in the console that opens?
Does a different pinentry work?

Doesn't look like T4347 in that no errors show
stopping daemons and restarting kleoptra "sometimes" fixes it and pinentry windows shows, until it does all operations fail with pinentry missing
running pinentry-qt.exe I get
Please note that you don't have secure memory on this system
OK Pleased to meet you
We seem to have stopped it happening by randomly changing settings - generating blank conf files, reinstalling pgp4win but cannot pinpoint exactly what change fixes the error and because it's intermittent we may just be getting lucky

aheinecke closed this task as Resolved.Apr 9 2019, 10:05 AM

As this task has no obvious next step I'm closing it.