aws / aws/amazon-q-developer-cli
update failed
- 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 7.0.0-28-generic - Ubuntu 24.04.4 LTS
### Expected behaviour
Le update work
### Actual behaviour
le update failed
### Steps to reproduce
don't know
### Environment
```yaml
[q-details]
version = "2.17.0"
hash = "7da34c8063ad9ec47e8307527141412363d95056"
date = "2026-08-07T19:28:48.560297Z (6d ago)"
variant = "minimal"
[system-info]
chip = "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz"
total-cores = 4
memory = "15.32 GB"
[system-info.os.linux]
kernel_version = "7.0.0-28-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/zsh"
shell-version = "5.9"
terminal = "Gnome Terminal"
install-method = "unknown"
[env-vars]
DISPLAY = ":0"
PATH = "/home/USER/.cargo/bin:/home/USER/bin:/home/USER/.local/bin:/home/USER/.config/emacs/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/local/bin:/opt/ghidra:/opt/ghidra/support"
QTERM_SESSION_ID = "8bd64ba8e9c94264b13728a053117f23"
QT_IM_MODULE = "ibus"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "2.17.0"
SHELL = "/usr/bin/zsh"
TERM = "xterm-256color"
XDG_CURRENT_DESKTOP = "ubuntu:GNOME"
XDG_SESSION_DESKTOP = "ubuntu"
XDG_SESSION_TYPE = "wayland"
XMODIFIERS = "@im=ibus"
```
Contributor guide
Research direction
Start by reproducing the update failure on Ubuntu 24.04 with version 2.17.0 after running `q doctor` and `q restart`. The report provides no reproduction steps, error output, logs, file, or test, so collect the failing command and diagnostic details before defining the fix and a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100