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 missing from dispatcher despite binary existing and working
Reported by TheRealGhost007 · 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 --no-sudo --print (the exact form documented for gathering
diagnostics before filing a bug) fails:
$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug --no-sudo --print
Run 'omarchy commands --all' to discover available commands.
omarchy commands --all doesn't list a debug group or any omarchy debug*
command at all.
What was expected
omarchy debug --no-sudo --print to run and print diagnostics, per the
command's own metadata and the project's documented bug-report workflow.
Steps to reproduce
omarchy debug --no-sudo --print
omarchy commands --all | grep -i debug # no output
The odd part
The actual binary is present and works fine when invoked directly, and its
header metadata looks identical in shape to other, correctly-indexed
commands:
$ head -6 /usr/bin/omarchy-debug
#!/bin/bash
# omarchy:summary=Print debugging information
# omarchy:args=[--no-sudo] [--print]
# omarchy:examples=omarchy debug --print --no-sudo
# omarchy:requires-sudo=true
$ omarchy-debug --no-sudo --print # works, prints full system report
So the dispatcher's command index appears to be silently dropping this one
specific command (possibly related to requires-sudo=true combined with
something else - didn't dig further into the indexer itself).
System details
- Omarchy: 4.0.2-1, stable channel
- Hyprland: 0.56.2
- Kernel: 7.1.9-arch1-2
- Machine: HP Laptop 17-by1xxx, Intel Core i5-8265U
View raw text
### What happened
`omarchy debug --no-sudo --print` (the exact form documented for gathering
diagnostics before filing a bug) fails:
$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug --no-sudo --print
Run 'omarchy commands --all' to discover available commands.
`omarchy commands --all` doesn't list a `debug` group or any `omarchy debug*`
command at all.
### What was expected
`omarchy debug --no-sudo --print` to run and print diagnostics, per the
command's own metadata and the project's documented bug-report workflow.
### Steps to reproduce
omarchy debug --no-sudo --print
omarchy commands --all | grep -i debug # no output
### The odd part
The actual binary is present and works fine when invoked directly, and its
header metadata looks identical in shape to other, correctly-indexed
commands:
$ head -6 /usr/bin/omarchy-debug
#!/bin/bash
# omarchy:summary=Print debugging information
# omarchy:args=[--no-sudo] [--print]
# omarchy:examples=omarchy debug --print --no-sudo
# omarchy:requires-sudo=true
$ omarchy-debug --no-sudo --print # works, prints full system report
So the dispatcher's command index appears to be silently dropping this one
specific command (possibly related to `requires-sudo=true` combined with
something else - didn't dig further into the indexer itself).
### System details
- Omarchy: 4.0.2-1, stable channel
- Hyprland: 0.56.2
- Kernel: 7.1.9-arch1-2
- Machine: HP Laptop 17-by1xxx, Intel Core i5-8265UValidation
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.