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 debug command is unreachable via the CLI router despite being advertised in --help
Reported by ajgorrell · filed Sep 4, 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
omarchy debug — listed in omarchy --help's "Common commands" section
("Print debugging information") and as its own top-level group
("Diagnostics and support logs") — is not actually dispatchable. Every
invocation fails:
$ omarchy debug
Unknown Omarchy command: omarchy debug
Run 'omarchy commands --all' to discover available commands.
$ omarchy debug --help
Unknown Omarchy command: omarchy debug --help
Run 'omarchy commands --all' to discover available commands.
$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug --no-sudo --print
Run 'omarchy commands --all' to discover available commands.omarchy commands --all (439 entries) has zero entries for the debug
group — it appears to be missing from the command registry entirely, even
though top-level --help still advertises it.
Root cause (best guess)
The underlying script still exists and works fine when called directly:
$ which omarchy-debug
/usr/bin/omarchy-debug
$ omarchy-debug --no-sudo --print
# ...works, produces the full diagnostic log...Note it lives at /usr/bin/omarchy-debug, not under/usr/share/omarchy/bin/ like other omarchy-* commands — so this looks
like a registration/packaging gap where the debug group's dispatch entry
was dropped from the command router (or the binary's location changed and
the router wasn't updated to find it there), while the static help text
listing it was left in place.
Steps to reproduce
- On an Omarchy install, run
omarchy debug(oromarchy --helpand try
the listed debug command).
2. Observe Unknown Omarchy command.
3. Run omarchy commands --all and confirm no debug-group entries appear.
4. Run omarchy-debug --no-sudo --print directly — it works.
Expected
omarchy debug (with --no-sudo --print etc.) should dispatch to/usr/bin/omarchy-debug like the help text says.
System details
Omarchy 4.0.2-1, Hyprland 0.56.2, Arch Linux.
Related
Found while diagnosing and reporting a different Windows VM bug
(#10256) — needed the diagnostic log for that report and hit this instead.
View raw text
## What happened
`omarchy debug` — listed in `omarchy --help`'s "Common commands" section
("Print debugging information") and as its own top-level group
("Diagnostics and support logs") — is not actually dispatchable. Every
invocation fails:
```
$ omarchy debug
Unknown Omarchy command: omarchy debug
Run 'omarchy commands --all' to discover available commands.
$ omarchy debug --help
Unknown Omarchy command: omarchy debug --help
Run 'omarchy commands --all' to discover available commands.
$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug --no-sudo --print
Run 'omarchy commands --all' to discover available commands.
```
`omarchy commands --all` (439 entries) has zero entries for the `debug`
group — it appears to be missing from the command registry entirely, even
though top-level `--help` still advertises it.
## Root cause (best guess)
The underlying script still exists and works fine when called directly:
```
$ which omarchy-debug
/usr/bin/omarchy-debug
$ omarchy-debug --no-sudo --print
# ...works, produces the full diagnostic log...
```
Note it lives at `/usr/bin/omarchy-debug`, not under
`/usr/share/omarchy/bin/` like other `omarchy-*` commands — so this looks
like a registration/packaging gap where the `debug` group's dispatch entry
was dropped from the command router (or the binary's location changed and
the router wasn't updated to find it there), while the static help text
listing it was left in place.
## Steps to reproduce
1. On an Omarchy install, run `omarchy debug` (or `omarchy --help` and try
the listed debug command).
2. Observe `Unknown Omarchy command`.
3. Run `omarchy commands --all` and confirm no `debug`-group entries appear.
4. Run `omarchy-debug --no-sudo --print` directly — it works.
## Expected
`omarchy debug` (with `--no-sudo --print` etc.) should dispatch to
`/usr/bin/omarchy-debug` like the help text says.
## System details
Omarchy 4.0.2-1, Hyprland 0.56.2, Arch Linux.
## Related
Found while diagnosing and reporting a different Windows VM bug
(#10256) — needed the diagnostic log for that report and hit this instead.
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.