aws / aws/amazon-q-developer-cli

kiro-cli-term fails to launch in ChromeOS Crostini - ld-linux-x86-64.so.2 not recognized as valid terminal

Open
#3,690 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
2k
Forks
439
PR merge metrics
No merged PRs in 30d

Description

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

Linux 6.6.99-09070-g0245f6566c20 - Debian GNU/Linux 12 (bookworm)

### Expected behaviour

I have installed Kiro on the linux VM running on my chromenook. Every time I open the application it goes through the all initialisation process: import from VS Code, choose theme, setup shell, ...

I would prefer for this configuration to be remembered and to not have errors when running kiro-cli

$ kiro-cli doctor

✘ bash ~/.bashrc integration check: /home/stever/.bashrc does not source post integration last

Run kiro-cli integrations install dotfiles to reinstall shell integrations for bash
Attempting to fix automatically...
Re-running check...

✔ bash ~/.bashrc integration check
✘ Kiro CLI terminal integrations: kiro-cli-term is not running in this terminal, please try restarting your terminal

✘ Doctor found errors. Please fix them and try again.

If you are not sure how to fix it, please open an issue with kiro-cli issue to let us know!

### Actual behaviour

Actual: should-figterm-launch returns exit code 1 with output:
❌ ld-linux-x86-64.so.2 | ld-linux-x86-64.so.2 (PID) <- ✅ bash (PID)

Crostini uses vshd (loaded via ld-linux-x86-64.so.2) to spawn bash. This isn't recognized as a valid terminal emulator, so kiro-cli-term never starts.

### Steps to reproduce

Steps to reproduce:
1. Install kiro-cli in a ChromeOS Crostini (Debian) Linux container
2. Open the default Crostini terminal
3. Run kiro-cli doctor
4. Run kiro-cli _ should-figterm-launch -vvv

Expected: kiro-cli-term launches normally

### Environment

```yaml
kiro-cli diagnostics

[q-details]
version = "1.21.0"
hash = "dc54efd85f411d6b4347d192733ff40650d38dfb"
date = "2025-11-26T22:30:26.062904Z (120d ago)"
variant = "minimal"

[system-info]
chip = "Intel(R) Core(TM) Ultra 7 155U"
total-cores = 14
memory = "13.85 GB"

[system-info.os.linux]
kernel_version = "6.6.99-09070-g0245f6566c20"
id = "debian"
name = "Debian GNU/Linux"
pretty_name = "Debian GNU/Linux 12 (bookworm)"
version_id = "12"
version = "12 (bookworm)"

[environment]
cwd = "/home/USER"
cli-path = "/home/USER"
os = "Linux"
shell-path = "/usr/bin/bash"
shell-version = "5.2.15"
install-method = "unknown"

[env-vars]
DISPLAY = ":0"
GTK_IM_MODULE = "cros"
PATH = "/home/USER/.local/bin:/home/USER/.local/bin:/home/USER/.config/nvm/versions/node/v22.17.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/USER/.local/bin"
Q_SET_PARENT_CHECK = "1"
SHELL = "/bin/bash"
TERM = "xterm-256color"
XDG_CURRENT_DESKTOP = "X-Generic"
XDG_SESSION_TYPE = "wayland"
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.