Terminal can't be closed when bundled gpg invokes

[bthiae2934]

Existing issues matching what you're seeing

• I was not able to find an open or closed issue matching what I'm seeing

Git for Windows version

git version 2.51.2.windows.1
cpu: x86_64
built from commit: bd2ecbae58213046a468256b95fc4864de25bdf5
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
feature: fsmonitor--daemon
libcurl: 8.16.0
OpenSSL: OpenSSL 3.5.4 30 Sep 2025
zlib: 1.3.1
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
default-ref-format: files
default-hash: sha1

Windows version

Windows 11

Windows CPU architecture

x86_64 (64-bit)

Additional Windows version information

Microsoft Windows [Version 10.0.26200.7171]

Options set during installation

Editor Option: VIM
Custom Editor Path:
Default Branch Option:
Path Option: Cmd
SSH Option: OpenSSH
Tortoise Option: false
CURL Option: WinSSL
CRLF Option: CRLFCommitAsIs
Bash Terminal Option: MinTTY
Git Pull Behavior Option: Merge
Use Credential Manager: Enabled
Performance Tweaks FSCache: Enabled
Enable Symlinks: Disabled
Enable FSMonitor: Disabled

Other interesting things

No response

Terminal/shell

Windows Terminal, PowerShell

Commands that trigger the issue

1. Create a new repo and make a commit with gpg signature.
2. Kill all process of keyboxd.exe.
3. git log --show-signature.
4. Type exit and Enter key to exit PowerShell.

Expected behaviour

The tab should close immediately.

Actual behaviour

The tab doesn't close and there's only a cursor. It's weird.

Repository

No response

[bthiae2934]

I troubleshooted this issue and found that process keyboxd.exe started by bundled gpg held a reference to the console so the tab didn't close. I attached process of keyboxd.exe with gdb of MSYS2, executed print (void)FreeConsole() and then the tab closed immediately.

[dscho]

@bthiae2934 is this also happening with a regular MSYS2?

[bthiae2934]

@bthiae2934 is this also happening with a regular MSYS2?

I tried the reproduction steps in Windows Terminal with MSYS2 ucrt64 environment and I can't reproduce it. The tab closed when I executed exit.

[dscho]

@bthiae2934 did you use the MSYS or the MINGW variant of gpg, i.e. what does type gpg show?

[bthiae2934]

@bthiae2934 did you use the MSYS or the MINGW variant of gpg, i.e. what does type gpg show?

REDACTED@REDACTED MSYS ~
$ type gpg
gpg is /usr/bin/gpg

REDACTED@REDACTED MSYS ~
$ gpg --version
gpg (GnuPG) 2.4.8
libgcrypt 1.11.2-unknown
Copyright (C) 2025 g10 Code GmbH
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/REDACTED/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

REDACTED@REDACTED MSYS ~
$ git --version
git version 2.51.2

REDACTED@REDACTED MSYS ~
$

I also tried the steps and the tab closed.

[dscho]

Hmm. I'd expect this gpg.exe to be identical to Git for Windows', and likewise its keyboxd.exe... The only difference is that MSYS2's git.exe is an MSYS one while Git for Windows' is a MINGW one.

[bthiae2934]

Hmm. I'd expect this gpg.exe to be identical to Git for Windows', and likewise its keyboxd.exe... The only difference is that MSYS2's git.exe is an MSYS one while Git for Windows' is a MINGW one.

Have you reproduced this issue in PowerShell with Windows Terminal successfully? I don't have debug symbol of git for windows which makes it extremely time consuming to troubleshoot it by myself.

[dscho]

I don't have an appropriate setup to test git log --verify-signatures, and am in the middle of something else.

If you want to have debug symbols, the best I can do is point you to https://gitforwindows.org/building-git

[dscho]

If you want to have debug symbols, the best I can do is point you to https://gitforwindows.org/building-git

I've meant for a long time to augment that page with more information such as how to run the just-built Git in place (/usr/src/git/bin-wrappers/git -C <your-worktree> [...]), but that keeps being pushed down on the list...

[bthiae2934]

I don't have an appropriate setup to test git log --verify-signatures

It's not difficult to generate a key and sign it, you don't need a hardware key. All you need is Windows Terminal and Git for Windows.

In Git Bash:

REDACTED@REDACTED MINGW64 /d/git-test
$ gpg --generate-key
gpg (GnuPG) 2.4.8; Copyright (C) 2025 g10 Code GmbH
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Note: Use "gpg --full-generate-key" for a full featured key generation dialog.

GnuPG needs to construct a user ID to identify your key.

Real name: test
Email address: test@test
You selected this USER-ID:
    "test <test@test>"

Change (N)ame, (E)mail, or (O)kay/(Q)uit? O
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: revocation certificate stored as '/c/Users/neonc/.gnupg/openpgp-revocs.d/BE8D7452137F6EBC581EA67B9FF3D6F27BBD6D4B.rev'
public and secret key created and signed.

pub   ed25519 2025-11-25 [SC] [expires: 2028-11-24]
      BE8D7452137F6EBC581EA67B9FF3D6F27BBD6D4B
uid                      test <test@test>
sub   cv25519 2025-11-25 [E] [expires: 2028-11-24]

cd /d/git-test
git init
touch README.md
git add README.md
git commit -SBBD6D4B

Then you can reproduce it in PowerShell.

[dscho]

All you need is Windows Terminal and Git for Windows.

... and time.

[bthiae2934]

All you need is Windows Terminal and Git for Windows.

... and time.

I'm in the same situation with another difficulty: I'm in China and it's difficult to pull code from github due to a "great" device on the network boundary of the country. It's sad that many open-source software is maintained by someone without a payment and they have their life to struggle with.

I know this issue is time consuming to troubleshoot and maybe we need to communicate with people from MSYS2 / MINGW / Cygwin. I decide to tell you that there's an issue and all the information I have figured out with limited time I can spare on this issue.

Feel free to keep or close this issue.

[dscho]

@bthiae2934 I feel for you. Let's keep this ticket open!