Post-commit blank screen (intermittently in zed terminal)

[hreynier]

Describe the bug

Occasionally after committing, instead of returning the lazygit I just get a blank screen.
I'm not sure what causes this, as it happens intermittently. I exclusively use Lazygit within the Zed editor built-in terminal, but this wasn't happening until a few weeks ago. I've upgraded to latest and I still see it happening.

To Reproduce

Steps to reproduce the behavior:

1. Commit a file in zed's built-in terminal
2. Press enter
3. See blank screen

Expected behavior

Expect to return back to Lazygit or at least gracefully exit lazygit

Screenshots

I've recorded my experience earlier here.

Screen.Recording.2025-10-11.at.12.30.12.mov

Version info:

lazygit commit=, build date=, build source=Homebrew, version=0.55.1, os=darwin, arch=arm64, git version=2.50.1
git git version 2.50.1

Additional context

I've tried running lazygit --debug to see if I can solve the issue I got this

Oct 11 12:54:10 |DEBU| RunCommand command="git -C /Users/user/Projects/metal-cpp-cmake-starter diff --no-ext-diff --submodule --unified=3 --color=always --find-renames=50% --no-index -- /dev/null cmake/MetalShaders.cmake"
Oct 11 12:54:10 |ERRO| Unexpected error when running cmd task: exit status 1; Failed command: /opt/homebrew/bin/git [git -C /Users/user/Projects/metal-cpp-cmake-starter diff --no-ext-diff --submodule --unified=3 --color=always --find-renames=50% --no-index -- /dev/null cmake/MetalShaders.cmake]
Oct 11 12:54:10 |DEBU| RunCommand command="git -C /Users/user/Projects/metal-cpp-cmake-starter diff --no-ext-diff --submodule --unified=3 --color=always --find-renames=50% --cached -- cmake/MetalShaders.cmake"
Oct 11 12:54:10 |INFO| postRefreshUpdate for files took 3.692416ms
Oct 11 12:54:10 |DEBU| RunCommand command="git add -- cmake/MetalShaders.cmake"
Oct 11 12:54:10 |INFO| git add -- cmake/MetalShaders.cmake (19.493958ms)
Oct 11 12:54:10 |INFO| refreshing the following scopes in async mode: files
Oct 11 12:54:10 |DEBU| using cache for key status.showUntrackedFiles
Oct 11 12:54:10 |INFO| Refresh took 266.625µs
Oct 11 12:54:10 |DEBU| RunCommand command="git status --untracked-files=all --porcelain -z --find-renames=50%"
Oct 11 12:54:10 |DEBU| RunCommand command="git -C /Users/user/Projects/metal-cpp-cmake-starter diff --no-ext-diff --submodule --unified=3 --color=always --find-renames=50% --cached -- cmake/MetalShaders.cmake"
Oct 11 12:54:10 |INFO| git status --untracked-files=all --porcelain -z --find-renames=50% (14.313792ms)
Oct 11 12:54:10 |INFO| postRefreshUpdate for submodules took 10.209µs

I dont' even see a log for committing weirdly and the only error I saw was around trying to see a diff on a file I committed.

Note

Please try updating to the latest version or manually building the latest master to see if the issue still occurs.

[stefanhaller]

I'm afraid I have no idea why this happens, but there might be a workaround: you can avoid suspending lazygit when you make a commit by including this in your config file:

git:
  overrideGpg

You might then still have the problem in other situations where lazygit suspends itself, i.e. when using shift-R to reword with an editor, or running a shell command at the : prompt. I don't have a workaround for those.

As for the "Unexpected error when running cmd task" in your log: that's harmless. Running git diff with --no-index implies --exit-code, which causes git to return with an exit code of 1 when there's a diff. The code higher up the call chain thinks that's an error and logs it. An easy fix would be to also include a --no-exit-code option in the command, but it doesn't seem to exit.