Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
omarchy update analyze logs fails with a raw grep error when the update log doesn't exist
Reported by vayners · filed Sep 10, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Description
When running omarchy update analyze logs standalone (outside the normal omarchy update flow),
the command fails with a raw grep error to stderr instead of a clean message:
grep: /tmp/omarchy-update.log: No such file or directoryRoot Cause
The /usr/share/omarchy/bin/omarchy-update-analyze-logs script greps /tmp/omarchy-update.log
without checking whether it exists first. This is fine when the command is called from inside
the main omarchy update flow, which uses script -qefc ... "/tmp/omarchy-update.log" to
create that file before invoking any sub-commands. However, omarchy update analyze logs is
also listed as a standalone user-facing command in omarchy commands --all, and running it
independently (e.g., right after boot) produces the raw error message.
Suggested Fix
Add an existence check before the grep operation, something like:
[[ -f "$update_log" ]] || exit 0Or print a friendlier message like "No update log found; nothing to analyze."
System Details
- omarchy version: 4.0.3-1
- omarchy-settings version: 4.0.3-1
Filed by Claude Haiku 4.5 via Claude Code.
View raw text
## Description When running `omarchy update analyze logs` standalone (outside the normal `omarchy update` flow), the command fails with a raw `grep` error to stderr instead of a clean message: ``` grep: /tmp/omarchy-update.log: No such file or directory ``` ## Root Cause The `/usr/share/omarchy/bin/omarchy-update-analyze-logs` script greps `/tmp/omarchy-update.log` without checking whether it exists first. This is fine when the command is called from inside the main `omarchy update` flow, which uses `script -qefc ... "/tmp/omarchy-update.log"` to create that file before invoking any sub-commands. However, `omarchy update analyze logs` is also listed as a standalone user-facing command in `omarchy commands --all`, and running it independently (e.g., right after boot) produces the raw error message. ## Suggested Fix Add an existence check before the grep operation, something like: ```bash [[ -f "$update_log" ]] || exit 0 ``` Or print a friendlier message like "No update log found; nothing to analyze." ## System Details - omarchy version: 4.0.3-1 - omarchy-settings version: 4.0.3-1 --- Filed by Claude Haiku 4.5 via Claude Code.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 11:32 UTC