Repository navigation
Conversation
Steam only knows exit 0 and 7, so every updater failure (not enough space, registry unreachable, bootc failing) shows up as "no updates". armada-update now records the result of each check and apply run in /var/lib/armada/update-status.json without changing exit codes or output. Armada Control reads it, shows an "Update Blocked" line in Settings and toasts after every blocked check and once per session. Network failures only show in Settings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related: #785, #328.
Problem
My Retroid Pocket 6 stayed on the 20261010 beta image for weeks after newer builds were published. Game Mode → Settings → System → Check for updates kept saying there were no updates. The reason was only in the journal:
/varwas 98% full (92 G partition), and nothing in the UI said so.Steam's update protocol has two answers: exit 0 for an available update or a successful install, and exit 7 for no update.
armada-updatesends every failure throughfail(), which logs and exits 7, so Steam reports "no updates" when space runs out, when the registry is unreachable, when the metadata is incomplete, when bootc or the target is missing, and whenbootc switchorbootc upgradefails. That last case is how the rpm-ostree layering error in #785 stays hidden. Since full storage can also break boot (#328), a visible low-space warning helps outside of updates too.Changes
armada-updatenow writes the result of every check and apply run to/var/lib/armada/update-status.json:{"time": 1794960981, "mode": "check", "result": "no_space", "target": "ghcr.io/armada-os/armada:testing", "version": "20261116.298ad1a", "needed_bytes": 1426703945, "reserve_bytes": 64424509440, "available_bytes": 12489785344}resultis one ofavailable,up_to_date,staged,no_space,remote_unreachable,bad_metadata,apply_failedorerror. The file is replaced atomically, and if the write fails the exit code stays the same. Exit codes and stdout are unchanged, so Steam sees no difference. Steam starts the updater throughpkexec(/usr/bin/steamos-polkit-helpers/steamos-update), so both modes run as r/lib/armada. The Armada Control backend reads and validates the file inget_update_sto part of the config, so the Settings tab needs no extra call.In the frontend, Settings shows an "Update Blocked" line under "OS Versios a failure, for example "Free up 5.8 GB of storage to install the nextArmada update." The amount includes the OSTree reserve and is rounded up. A toast appears after every blocked check, including a manual "Check for updates", and once per session while the update stays blocked. The first poll runs 30 s after Stm drops toasts sent during startup.
remote_unreachableonly shows inSettings, since a short network outage shouldn't pop up a toast. The strings are translated for en, pt-BR, pt-PT and zh-CN.Open questions
/var/lib/armada/update-status.jsona good place, or would you prefer/run?/runis cleared on reboot, which may fit a "last check" result better.apply_failedinclude bootc's last error line, such as the rpm-om OS update silently stuck: Steam says "up to date" when the deployment has rpm-ostree layered packages #785, so the UI can show it? For now the message points tojournalctl-t armada-update.journalctl -t armada-update -o jsonand no shell changes. That diff would be smaller, but it depends on log textthat can change at any time, so I chose the status file.Testing
tests/desktop-update-test.pyhas new cases that check the recorded result for available, no_space (check and apply), remote_unreachable, up_to_date and staged (check andapply), and that an unwritable status path leaves the exit code and output.sh
,update-migration-test.shandupdate-progress-test.sh` stillpass.decky/armada-control,npm testpasses with 52 tests, including ttest.tswith the numbers from my journal, and the i18n parity check.npm run build` succeeds./tmpw{"result": "up_to_date", "target": "ghcr.io/armada-os/armada:beta", "version": "20261109.dfed5d6"}.no_space, a test copy checked the testing channel with the resexited 7, logged the usual "update does not fit" lines and wrote the status JSON shown above.