Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-4880GitHub issuePublicReceived

omarchy debug --no-sudo --print does not exist in 4.0.2-1

Reported by jandal · 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.

Received and recorded verbatim. Nothing has been checked yet.

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

omarchy debug --no-sudo --print does not exist in 4.0.2-1revision 1 · captured 2026-10-04 12:10 UTC via poll

The contributing/support docs reference generating diagnostics with:

omarchy debug --no-sudo --print

On Omarchy 4.0.2-1 this command doesn't exist:

$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug --no-sudo --print
Run 'omarchy commands --all' to discover available commands.

omarchy commands --all has no debug group and nothing else that produces an equivalent system/diagnostics dump (checked for debug, diag, report in the command list).

Either the debug command needs to be restored/implemented, or the docs pointing users at it for bug reports need updating to whatever the current equivalent is.

(Split out from #10127, where this was noticed as a side effect while filing that report.)

View raw text
The contributing/support docs reference generating diagnostics with:

```
omarchy debug --no-sudo --print
```

On Omarchy 4.0.2-1 this command doesn't exist:

```
$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug --no-sudo --print
Run 'omarchy commands --all' to discover available commands.
```

`omarchy commands --all` has no `debug` group and nothing else that produces an equivalent system/diagnostics dump (checked for `debug`, `diag`, `report` in the command list).

Either the `debug` command needs to be restored/implemented, or the docs pointing users at it for bug reports need updating to whatever the current equivalent is.

(Split out from #10127, where this was noticed as a side effect while filing that report.)

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.