kiro-cli keyboard input no response

### 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.8.0-134-generic - Ubuntu 24.04.4 LTS

### Expected behaviour

kiro-cli launched and I should be able to input command

### Actual behaviour

1. kiro-cli launched but keyboard input no response.

2. kiro-cli doctor reported:
GTK_IM_MODULE is not set to `ibus`. This may cause autocomplete to break in some terminals.
✘ GNOME Shell Extension Check: The Kiro CLI GNOME extension is installed but not loaded. Please restart your login session and try again.

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

3. kiro-cli restart reported:
Launching Kiro CLI...
error: Kiro CLI was unable launch successfully

Please advise how to resolve this problem

### Steps to reproduce

1. kiro-cli launched but keyboard input no response.

2. kiro-cli doctor reported:
GTK_IM_MODULE is not set to `ibus`. This may cause autocomplete to break in some terminals.
✘ GNOME Shell Extension Check: The Kiro CLI GNOME extension is installed but not loaded. Please restart your login session and try again.

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

3. kiro-cli restart reported:
Launching Kiro CLI...
error: Kiro CLI was unable launch successfully

### Environment

```yaml

[q-details]
version = "2.12.1"
hash = "be67981a261e439b93d8dbe5f3e398b383f00aea"
date = "2026-07-09T21:56:06.36343Z (5d ago)"
variant = "full"

[system-info]
chip = "Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz"
total-cores = 1
memory = "3.81 GB"

[system-info.os.linux]
kernel_version = "6.8.0-134-generic"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 24.04.4 LTS"
version_id = "24.04"
version = "24.04.4 LTS (Noble Numbat)"

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

[env-vars]
DISPLAY = ":0"
PATH = "/home/USER/.nvm/versions/node/v20.20.2/bin:/home/USER/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/home/USER/.dotnet/tools:/usr/local/go/bin"
QTERM_SESSION_ID = "9ac67eaeb0d447d3913780f69b4c79e9"
QT_IM_MODULE = "ibus"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "2.12.1"
SHELL = "/bin/bash"
TERM = "xterm-256color"
XDG_CURRENT_DESKTOP = "ubuntu:GNOME"
XDG_SESSION_DESKTOP = "ubuntu"
XDG_SESSION_TYPE = "wayland"
XMODIFIERS = "@im=ibus"
```

Inizia riproducendo il malfunzionamento dell’input da tastiera nell’ambiente GNOME Terminal con Ubuntu 24.04 indicato, quindi confronta le diagnosi di `q doctor` e `q restart`. Nell’issue non sono identificati né un file sorgente né un test; il lavoro è completato quando la causa è stata determinata e l’input interattivo da tastiera è stato ripristinato, senza gli errori di avvio o di doctor segnalati.

Scritto dal modello di indicizzazione a partire dal testo della issue.