Proof Portal

Sign in
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-1613GitHub issuePublicDecided· Out of scope

Bar: every inline command module logs TypeError: Cannot assign to read-only property "moduleName"

Reported by jeremy · filed Aug 20, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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

Bar: every inline command module logs TypeError: Cannot assign to read-only property "moduleName"revision 1 · captured 2026-09-28 21:29 UTC via poll

Every instantiation of an inline type: "command" bar module logs this warning twice (as of 94554969):

Aug 20 10:19:12 thelio omarchy-shell[2779]:   WARN scene: @plugins/bar/Bar.qml[1751:-1]: TypeError: Cannot assign to read-only property "moduleName"
Aug 20 10:19:12 thelio omarchy-shell[2779]:   WARN scene: @plugins/bar/Bar.qml[1751:-1]: TypeError: Cannot assign to read-only property "moduleName" (exception occurred during delayed function evaluation)

One-line diagnosis: injectProps() (shell/plugins/bar/Bar.qml:1754) does target.moduleName = moduleName guarded only by "moduleName" in target, but CustomCommandModule declares readonly property string moduleName (Bar.qml:1768) — the in check passes for readonly properties, so the assignment throws on every inline command-module slot.

Harmless in practice — the readonly property already computes the same value from entry — but it fires on every command module the user configures, and the thrown TypeError also aborts injectProps() before the settings assignment on the next line, which would matter if a command module ever grew a writable settings dependency.

Reproduce: add any inline command module to bar.layout in ~/.config/omarchy/shell.json and watch journalctl --user -f.

View raw text
Every instantiation of an inline `type: "command"` bar module logs this warning twice (as of `94554969`):

```
Aug 20 10:19:12 thelio omarchy-shell[2779]:   WARN scene: @plugins/bar/Bar.qml[1751:-1]: TypeError: Cannot assign to read-only property "moduleName"
Aug 20 10:19:12 thelio omarchy-shell[2779]:   WARN scene: @plugins/bar/Bar.qml[1751:-1]: TypeError: Cannot assign to read-only property "moduleName" (exception occurred during delayed function evaluation)
```

One-line diagnosis: `injectProps()` (`shell/plugins/bar/Bar.qml:1754`) does `target.moduleName = moduleName` guarded only by `"moduleName" in target`, but `CustomCommandModule` declares `readonly property string moduleName` (`Bar.qml:1768`) — the `in` check passes for readonly properties, so the assignment throws on every inline command-module slot.

Harmless in practice — the readonly property already computes the same value from `entry` — but it fires on every command module the user configures, and the thrown TypeError also aborts `injectProps()` before the `settings` assignment on the next line, which would matter if a command module ever grew a writable `settings` dependency.

Reproduce: add any inline command module to `bar.layout` in `~/.config/omarchy/shell.json` and watch `journalctl --user -f`.

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 08:14 UTC