Pinentry won't show up
Closed, ResolvedPublic

Description

Hello. I just upgraded to 2.2.26 from 2.2.24 on Vista 32-bit (100% clean install) and I can't seem to get gpg to work. Particularly pinentry doesn't show up at all when called, though it remains active in the background, taking neither extra memory nor extra CPU cycles.

Interestingly enough, it did appear to work first time around, but then it just stopped. I think deleting gpg.conf and temporary files from Roaming\gnupg before running it the second time may have triggered this behavior, but I can't double-check right now (May be able to pretty soon anyways). I saved one of the logs just in case there's something relevant in there:

C:\>echo Hello, world!|gpg --armor --symmetric --debug-level guru
gpg: enabled debug flags: packet mpi crypto filter iobuf memory cache memstat trust hashing ipc clock lookup extprog
gpg: DBG: [not enabled in the source] start
gpg: DBG: fd_cache_invalidate (C:/Users/Me/AppData/Roaming/gnupg/pubring.kbx)
gpg: DBG: iobuf-1.0: open 'C:/Users/Me/AppData/Roaming/gnupg/pubring.kbx' desc=file_filter(fd) fd=196
gpg: DBG: iobuf-1.0: close 'file_filter(fd)'
gpg: DBG: C:/Users/Me/AppData/Roaming/gnupg/pubring.kbx: close fd/handle 196
gpg: DBG: fd_cache_close (C:/Users/Me/AppData/Roaming/gnupg/pubring.kbx) new slot created
gpg: DBG: iobuf-*.*: ioctl 'C:/Users/Me/AppData/Roaming/gnupg/pubring.kbx' invalidate
gpg: DBG: fd_cache_invalidate (C:/Users/Me/AppData/Roaming/gnupg/pubring.kbx)
gpg: DBG:                 did (C:/Users/Me/AppData/Roaming/gnupg/pubring.kbx)
gpg: keybox 'C:/Users/Me/AppData/Roaming/gnupg/pubring.kbx' created
gpg: DBG: iobuf-2.0: open '[stdin]' desc=file_filter(fd) fd=100
gpg: DBG: iobuf-2.0: ioctl 'file_filter(fd)' no_cache=1
gpg: no running gpg-agent - starting 'C:\Program Files\gnupg\bin\gpg-agent.exe'
gpg: waiting for the agent to come up ... (5s)
gpg: DBG: chan_0x00000110 <- OK Pleased to meet you
gpg: connection to agent established
gpg: DBG: chan_0x00000110 -> RESET
gpg: DBG: chan_0x00000110 <- OK
gpg: DBG: chan_0x00000110 -> GETINFO version
gpg: DBG: chan_0x00000110 <- D 2.2.26
gpg: DBG: chan_0x00000110 <- OK
gpg: DBG: chan_0x00000110 -> OPTION allow-pinentry-notify
gpg: DBG: chan_0x00000110 <- OK
gpg: DBG: chan_0x00000110 -> OPTION agent-awareness=2.1.0
gpg: DBG: chan_0x00000110 <- OK
gpg: DBG: chan_0x00000110 -> GETINFO cmd_has_option GET_PASSPHRASE repeat
gpg: DBG: chan_0x00000110 <- OK
gpg: DBG: chan_0x00000110 -> GETINFO cmd_has_option GET_PASSPHRASE newsymkey
gpg: DBG: chan_0x00000110 <- OK
gpg: DBG: chan_0x00000110 -> GET_PASSPHRASE --data --repeat=1 --check --newsymkey -- S7D9B73D963D0A270 X X Enter+passphrase%0A

At that point I had to ctrl+c to cancel the process because it wouldn't do anything.

Best regards and Merry Christmas :)

Details

Version
2.2.26 on Vista 32-bit
werner added a subscriber: werner.Wed, Dec 23, 10:27 PM

Simply add -v or --verbose to the gpg invocation too see infos about the pinentry. --debug-level is not helpful here.
And well, we don't have a way to test stuff on Vista anymore. You should also update to at least Windows 7.

werner triaged this task as Normal priority.
werner raised the priority of this task from Normal to Needs Triage.
werner edited projects, added No Response; removed Bug Report.Mon, Jan 18, 12:26 PM
werner closed this task as Resolved.
werner claimed this task.