gemini-cli - 💡(How to fix) Fix ioctl(2) failed, EBADF

What happened?

While the Gemini CLI was executing a shell command (chmod +x docker/bin/entrypoint.sh), it encountered a critical crash in the underlying terminal handling logic.

Technical Details:

• Error: Error: ioctl(2) failed, EBADF (Bad File Descriptor).
• Location: The failure occurred inside node-pty (unixTerminal.js:243:13) during a pty.resize operation.
• Context: The stack trace indicates that a React-style hook (commitPassiveMountOnFiber) triggered a PTY resize while the shell execution was active. The EBADF error suggests that the file descriptor for the pseudo-terminal was either invalid, already closed, or not properly initialized when the resize was attempted.
• Impact: The CLI process terminated unexpectedly, although the shell command itself may have been sent to the OS before the crash.

chat_export.json

What did you expect to happen?

The shell command (chmod +x ...) should have executed successfully without crashing the application. I expected the CLI to remain stable and return the command's output (or exit code) so the agent could proceed to the next task. The internal terminal management (PTY) should handle resizing and initialization gracefully without throwing EBADF or triggering a critical process-level error.

Client information

• CLI Version: 0.44.0
• Git Commit: 1000b33d4
• Session ID: 2521dd80-4e95-4aad-8b8f-8feae28b5ea2
• Operating System: linux v20.20.2
• Sandbox Environment: no sandbox
• Model Version: auto
• Auth Type: oauth-personal
• Memory Usage: 281.5 MB
• Terminal Name: VTE(7600)
• Terminal Background: #222b30
• Kitty Keyboard Protocol: Unsupported

Login information

I'm logged in through my Google Account

Anything else we need to know?

No response