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-5054GitHub issuePublicReceived

omarchy plugin clone omarchy.bar: cloned bar plugin never mounts (layer-shell surface not created)

Reported by dhruva-nu · filed Sep 12, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #6915 (R-1851). 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 plugin clone omarchy.bar: cloned bar plugin never mounts (layer-shell surface not created)revision 1 · captured 2026-10-04 12:10 UTC via poll

What happened

Cloning the built-in bar-kind plugin with omarchy plugin clone omarchy.bar produces a plugin that omarchy plugin list --json reports as enabled: true, active: true, but the bar's layer-shell surface is never actually created — no bar renders, no screen space is reserved, and the cloned plugin's QML root shows spurious "Required property ... was not initialized" warnings in the journal on every load.

This reproduces with a byte-for-byte unmodified copy of the stock Bar.qml placed at the cloned path — it is not specific to any edits made after cloning.

Expected

Cloning omarchy.bar (a first-party bar-kind plugin) and switching to it should produce a working bar identical to the stock one, the same way cloning a bar-widget-kind plugin (e.g. omarchy.workspaces, omarchy.menu) works correctly.

Steps to reproduce

omarchy plugin clone omarchy.bar
# -> "Cloned omarchy.bar to <user>.bar and switched to <user>.bar"
omarchy plugin list --json | jq '.[] | select(.id=="<user>.bar" or .id=="omarchy.bar")'
# -> <user>.bar reports enabled:true, active:true
omarchy restart shell
hyprctl layers -j | jq '[.[].levels[][].namespace]'
# -> only ["omarchy-background"], "omarchy-bar" namespace is missing entirely
hyprctl monitors -j | jq '.[].reserved'
# -> [0,0,0,0], no exclusion zone reserved (stock bar reserves e.g. [0,26,0,0])

Journal (journalctl -t omarchy-shell) shows, on every load of the cloned plugin (even fully unedited):

WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[22:3]: Required property barConfig was not initialized
WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[17:3]: Required property barWidgetRegistry was not initialized
WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[15:3]: Required property omarchyPath was not initialized
WARN scene: @shell.qml[256:-1]: ReferenceError: errorString is not defined

Switching back with omarchy plugin enable omarchy.bar immediately restores the working stock bar, confirming the break is specific to loading a bar-kind plugin from the cloned/user plugin path rather than the first-party path.

System details

  • Omarchy version: 4.0.1-1
  • Kernel: Linux 7.1.9-arch1-2 #1 SMP PREEMPT_DYNAMIC Fri, 21 Aug 2026
  • GPU: Intel Meteor Lake-P (Intel Arc Graphics, integrated)
  • Compositor: Hyprland, shell: Quickshell (omarchy-shell)

Notes

  • omarchy debug --no-sudo --print is not a recognized command on this install (omarchy commands --all has no debug entry), so I couldn't attach that report — happy to provide anything else needed.
  • I could not find the actual underlying QML compile/runtime error, since the shell's own error-reporting path for this case throws (ReferenceError: errorString is not defined in shell.qml), which looks like a secondary bug masking the real diagnostic.

🤖 Filed with Claude Code

View raw text
## What happened

Cloning the built-in `bar`-kind plugin with `omarchy plugin clone omarchy.bar` produces a plugin that `omarchy plugin list --json` reports as `enabled: true, active: true`, but the bar's layer-shell surface is never actually created — no bar renders, no screen space is reserved, and the cloned plugin's QML root shows spurious "Required property ... was not initialized" warnings in the journal on every load.

This reproduces with a **byte-for-byte unmodified copy** of the stock `Bar.qml` placed at the cloned path — it is not specific to any edits made after cloning.

## Expected

Cloning `omarchy.bar` (a first-party `bar`-kind plugin) and switching to it should produce a working bar identical to the stock one, the same way cloning a `bar-widget`-kind plugin (e.g. `omarchy.workspaces`, `omarchy.menu`) works correctly.

## Steps to reproduce

```bash
omarchy plugin clone omarchy.bar
# -> "Cloned omarchy.bar to <user>.bar and switched to <user>.bar"
omarchy plugin list --json | jq '.[] | select(.id=="<user>.bar" or .id=="omarchy.bar")'
# -> <user>.bar reports enabled:true, active:true
omarchy restart shell
hyprctl layers -j | jq '[.[].levels[][].namespace]'
# -> only ["omarchy-background"], "omarchy-bar" namespace is missing entirely
hyprctl monitors -j | jq '.[].reserved'
# -> [0,0,0,0], no exclusion zone reserved (stock bar reserves e.g. [0,26,0,0])
```

Journal (`journalctl -t omarchy-shell`) shows, on every load of the cloned plugin (even fully unedited):

```
WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[22:3]: Required property barConfig was not initialized
WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[17:3]: Required property barWidgetRegistry was not initialized
WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[15:3]: Required property omarchyPath was not initialized
WARN scene: @shell.qml[256:-1]: ReferenceError: errorString is not defined
```

Switching back with `omarchy plugin enable omarchy.bar` immediately restores the working stock bar, confirming the break is specific to loading a `bar`-kind plugin from the cloned/user plugin path rather than the first-party path.

## System details

- Omarchy version: 4.0.1-1
- Kernel: `Linux 7.1.9-arch1-2 #1 SMP PREEMPT_DYNAMIC Fri, 21 Aug 2026`
- GPU: Intel Meteor Lake-P (Intel Arc Graphics, integrated)
- Compositor: Hyprland, shell: Quickshell (`omarchy-shell`)

## Notes

- `omarchy debug --no-sudo --print` is not a recognized command on this install (`omarchy commands --all` has no `debug` entry), so I couldn't attach that report — happy to provide anything else needed.
- I could not find the actual underlying QML compile/runtime error, since the shell's own error-reporting path for this case throws (`ReferenceError: errorString is not defined` in `shell.qml`), which looks like a secondary bug masking the real diagnostic.

🤖 Filed with [Claude Code](https://claude.com/claude-code)

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.