Amazon Q IDE-Style Completions Not Showing in Gnome Terminal on Debian Linux

[yazanzaid00]

Checks

• I have searched github.com/aws/amazon-q-developer-cli/issues and there are no duplicates of my issue
• I have run q doctor in the affected terminal session
• I have run q restart and replicated the issue again

Operating system

Linux 6.6.20-aufs-1 - Debian GNU/Linux 12 (bookworm) 5785

Expected behaviour

Amazon Q Developer CLI should provide IDE-style inline completions for commands (e.g., git, docker, npm) in the terminal as described in the documentation.

Actual behaviour

No IDE-style completions are appearing in the terminal. Other features of Amazon Q Developer CLI are working correctly, but inline completions are not functional. I am connected via VNC
Error messages encountered:
• Xlib: extension "XInputExtension" missing on display ":5"
• Gdk-CRITICAL: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

Steps to reproduce

1. Downloaded and installed Amazon Q without root/sudo permissions.
2. Tested various commands like git status, docker ps, but no completions appeared.
3. other comands such as q chat, q translate all works expectedly

Environment

[q-details]
version = "1.5.1"
hash = "43f92e418e96c7beaa3e881f299241c15ba65900"
date = "2024-12-13T00:56:34.608318Z (25d ago)"
variant = "full"

[system-info]
chip = "Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz"
total-cores = 12
memory = "251.81 GB"

[system-info.os.linux]
kernel_version = "6.6.20-aufs-1"
id = "debian"
name = "Debian GNU/Linux"
pretty_name = "CS HUJI Debian GNU/Linux 12 (bookworm) 5785"
version_id = "12"
version = "12 (bookworm)"

[environment]
cwd = "/cs/usr/USER"
cli-path = "/cs/usr/USER"
os = "Linux"
shell-path = "/usr/bin/zsh"
shell-version = "5.9"
terminal = "Gnome Terminal"
install-method = "unknown"

[brandonskiser]

Are you seeing those error messages when trying to launch the desktop app? Is this using GNOME or some other desktop environment?

I'm assuming you're doing some SSH X11 forwarding, not entirely sure which part could be failing. Can you share some more details about your environment?