All Shell commands fail with "Command terminated by signal: 1"

[fbenati]

What happened?

Every script that the Shell tool tries to run (either by asking or if invoked with custom commands) terminates in error with "Command terminated by signal: 1"

What did you expect to happen?

Scripts terminate with 0 exit code and desired output (script correctness tried with manual execution in the terminal)

Client information

• CLI Version: 0.23.0
• Git Commit: 3ff0558
• Session ID: ab1cd003-12e8-4273-bd08-689657475932
• Operating System: linux v24.3.0
• Sandbox Environment: no sandbox
• Model Version: gemini-3-flash-preview
• Memory Usage: 456.5 MB
• Terminal Name: xterm.js(6.1.0-beta.91)
• Terminal Background: #181818
• Kitty Keyboard Protocol: Unsupported
• IDE Client: VS Code

Login information

Google Account

Anything else we need to know?

I am using WSL2 with Debian distro. Problem occurs when gemini-cli is executed both from VS Code terminal pane or Windows Terminal.

[gemini-cli]

Found possible duplicate issues:

• Command exited with code: 1 #13584

If you believe this is not a duplicate, please remove the status/possible-duplicate label.

[fbenati]

Not a duplicate of #13584, restarting the terminal or cleaning ~/.gemini/tmp/ folder does not help. Also, I am unable to remove the possible-duplicate label.

[aswinashok44]

Is this issue still happening? I tried running gemini-cli from Vscode and Windows terminal (Ubuntu 22.04) and shell commands ran fine.

[fbenati]

I have updated to 0.26 and it's still happening. Additionally, it seems that something has crashed and the cli is now stuck and does not respond to Ctrl+C making it impossible to exit it. See the attached screenshots. I am available to provide log files for additional troubleshooting.

[fbenati]

Additional evidence:

[SUNDRAM07]

Hi! I'd like to work on this issue.

I've been contributing to Gemini CLI (see PR #19935) and I've traced the root cause:

In

shellExecutionService.ts
, both the PTY path (

executeWithPty
) and the

childProcessFallback
path spawn shell commands without trapping SIGHUP. On WSL2, the PTY lifecycle can send spurious SIGHUP (signal 1) to the child process group — especially when running inside VS Code's nested terminal (xterm.js). This causes every shell command to terminate immediately with "Command terminated by signal: 1".

Proposed fix: Wrap spawned commands with trap '' HUP to ignore the spurious hangup signal. This is safe because Gemini CLI already uses explicit SIGTERM/SIGKILL via

killProcessGroup()
for process cleanup, making SIGHUP unnecessary for lifecycle management.

I'll submit a PR shortly with the fix and tests.

/assign