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 4.0.2 package omits omarchy-debug while bundled tools require omarchy debug
Reported by nontradition · filed Aug 31, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #7060 (R-1805). GitHub close reason: completed.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
What happened
On a complete Omarchy 4.0.2-1 installation, the documented debug command is unavailable:
$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug --no-sudo --print
Run 'omarchy commands --all' to discover available commands.
omarchy commands --all contains no debug command.
Expected behavior
omarchy debug --no-sudo --print should generate the diagnostic report requested by Omarchy's bundled troubleshooting and crash-reporting instructions.
Evidence
Installed package:
$ omarchy version
4.0.2-1
The package does not contain the expected command:
$ test -e /usr/share/omarchy/bin/omarchy-debug
# exit status 1
The package is otherwise complete:
$ pacman -Qk omarchy
omarchy: 1678 total files, 0 missing files
Therefore, the executable was omitted from the package manifest rather than deleted locally.
The installed Omarchy files still instruct users and agents to run the missing command:
/usr/share/omarchy/default/agents/skills/omarchy/SKILL.md
/usr/share/omarchy/default/agents/skills/omarchy/contributing.md
/usr/share/omarchy/default/agents/skills/diagnose-crash/reporting.md
For example, diagnose-crash/reporting.md requires:
omarchy debug --no-sudo --print
The official quattro source currently contains bin/omarchy-debug, but the stable 4.0.2-1 package does not install it.
Steps to reproduce
- Install or update to the stable
omarchy4.0.2-1 package. - Run
omarchy debug --no-sudo --print. - Observe
Unknown Omarchy command. - Run
pacman -Qk omarchyand confirm the package has no missing files. - Inspect the package file list and confirm
omarchy-debugis absent.
Impact
Users cannot generate the standard diagnostic report requested by Omarchy's own bug-reporting workflow. This also prevents the bundled crash-diagnosis agent from collecting the expected system diagnostics.
Manually copying the development-branch script into /usr/share/omarchy/bin is not an appropriate workaround because that directory is package-managed and updates would overwrite it.
Filed by GPT-5 via Codex.
View raw text
## What happened
On a complete Omarchy 4.0.2-1 installation, the documented debug command is unavailable:
$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug --no-sudo --print
Run 'omarchy commands --all' to discover available commands.
`omarchy commands --all` contains no `debug` command.
## Expected behavior
`omarchy debug --no-sudo --print` should generate the diagnostic report requested by Omarchy's bundled troubleshooting and crash-reporting instructions.
## Evidence
Installed package:
$ omarchy version
4.0.2-1
The package does not contain the expected command:
$ test -e /usr/share/omarchy/bin/omarchy-debug
# exit status 1
The package is otherwise complete:
$ pacman -Qk omarchy
omarchy: 1678 total files, 0 missing files
Therefore, the executable was omitted from the package manifest rather than deleted locally.
The installed Omarchy files still instruct users and agents to run the missing command:
/usr/share/omarchy/default/agents/skills/omarchy/SKILL.md
/usr/share/omarchy/default/agents/skills/omarchy/contributing.md
/usr/share/omarchy/default/agents/skills/diagnose-crash/reporting.md
For example, `diagnose-crash/reporting.md` requires:
omarchy debug --no-sudo --print
The official `quattro` source currently contains `bin/omarchy-debug`, but the stable 4.0.2-1 package does not install it.
## Steps to reproduce
1. Install or update to the stable `omarchy` 4.0.2-1 package.
2. Run `omarchy debug --no-sudo --print`.
3. Observe `Unknown Omarchy command`.
4. Run `pacman -Qk omarchy` and confirm the package has no missing files.
5. Inspect the package file list and confirm `omarchy-debug` is absent.
## Impact
Users cannot generate the standard diagnostic report requested by Omarchy's own bug-reporting workflow. This also prevents the bundled crash-diagnosis agent from collecting the expected system diagnostics.
Manually copying the development-branch script into `/usr/share/omarchy/bin` is not an appropriate workaround because that directory is package-managed and updates would overwrite it.
Filed by GPT-5 via Codex.
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.
No decision has been recorded yet.