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

Cloning a "kind: bar" plugin (omarchy plugin clone omarchy.bar) never renders

Reported by Charlieras262 · filed Aug 24, 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

Cloning a "kind: bar" plugin (omarchy plugin clone omarchy.bar) never rendersrevision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

Cloning the omarchy.bar plugin (omarchy plugin clone omarchy.bar) produces a bar that never renders. After the clone (which also switches ~/.config/omarchy/shell.json's bar.id to the new plugin), the top bar disappears entirely -- no omarchy-bar layer-shell surface is created at all.

This reproduces with a byte-for-byte unedited clone -- it's not caused by modifying Bar.qml, only by cloning and activating it.

What I expected

Cloning omarchy.bar (a "kinds": ["bar"] plugin) should behave like cloning a bar-widget plugin (e.g. omarchy.workspaces) does: the clone becomes the active bar and renders identically to the stock one until edited.

Steps to reproduce

omarchy plugin clone omarchy.bar
# output: "Cloned omarchy.bar to ~/.config/omarchy/plugins/<user>.bar and switched to <user>.bar"
hyprctl layers | grep -oE "namespace: .*" | sort -u

Expected: omarchy-bar (and omarchy-background) in the namespace list.
Actual: only omarchy-background (and sometimes omarchy-notifications) -- the bar's layer surface is never mapped.

Revert with omarchy bar use omarchy.bar to confirm the stock bar comes back immediately (it does).

Diagnostics

journalctl --user -b 0 shows this immediately after the clone/switch, before any edit to the cloned file:

WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[15:3]: Required property omarchyPath 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[22:3]: Required property barConfig was not initialized

No Loader.Error / "bar option ... failed to load" message is logged, so the pluginBarLoader in shell.qml does appear to reach onLoaded and call configureBar(item, ...) -- but the bar still never maps a layer-shell surface.

My read of shell.qml (happy to be corrected): the stock bar loads via sourceComponent: defaultBarComponent, a Component whose Bar { omarchyPath: ...; barWidgetRegistry: ...; barConfig: ... } properties are bound at declaration, satisfying the required property fields in Bar.qml's root Item at construction time. A cloned bar instead loads via pluginBarLoader's Loader { source: shell.activeBarSourceUrl } (async, URL-based) -- QML's declarative Loader.source has no way to supply initial property values, so the three required property fields are necessarily unset at construction, only assigned afterward via configureBar. Whatever depends on those properties being present at construction for a PanelWindow/layer-shell surface to map correctly seems to never recover once that happens.

System details

  • Omarchy version: 4.0.0-1
  • Kernel: 7.1.8-arch1-3
  • CPU: Intel (Alder Lake-S)
  • GPU: Intel UHD 770 (i915) + NVIDIA GeForce RTX 5070 (nvidia-open-dkms 610.57.04)
  • Bar position: top, default (non-cloned) bar otherwise working fine

Workaround

None currently -- any customization that requires cloning the whole bar (rather than an individual bar-widget) hits this. Reverted to the stock omarchy.bar for now with omarchy bar use omarchy.bar.

View raw text
## What happened

Cloning the `omarchy.bar` plugin (`omarchy plugin clone omarchy.bar`) produces a bar that never renders. After the clone (which also switches `~/.config/omarchy/shell.json`'s `bar.id` to the new plugin), the top bar disappears entirely -- no `omarchy-bar` layer-shell surface is created at all.

This reproduces with a **byte-for-byte unedited clone** -- it's not caused by modifying `Bar.qml`, only by cloning and activating it.

## What I expected

Cloning `omarchy.bar` (a `"kinds": ["bar"]` plugin) should behave like cloning a `bar-widget` plugin (e.g. `omarchy.workspaces`) does: the clone becomes the active bar and renders identically to the stock one until edited.

## Steps to reproduce

```bash
omarchy plugin clone omarchy.bar
# output: "Cloned omarchy.bar to ~/.config/omarchy/plugins/<user>.bar and switched to <user>.bar"
hyprctl layers | grep -oE "namespace: .*" | sort -u
```

Expected: `omarchy-bar` (and `omarchy-background`) in the namespace list.
Actual: only `omarchy-background` (and sometimes `omarchy-notifications`) -- the bar's layer surface is never mapped.

Revert with `omarchy bar use omarchy.bar` to confirm the stock bar comes back immediately (it does).

## Diagnostics

`journalctl --user -b 0` shows this immediately after the clone/switch, before any edit to the cloned file:

```
WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[15:3]: Required property omarchyPath 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[22:3]: Required property barConfig was not initialized
```

No `Loader.Error` / "bar option ... failed to load" message is logged, so the `pluginBarLoader` in `shell.qml` does appear to reach `onLoaded` and call `configureBar(item, ...)` -- but the bar still never maps a layer-shell surface.

My read of `shell.qml` (happy to be corrected): the stock bar loads via `sourceComponent: defaultBarComponent`, a `Component` whose `Bar { omarchyPath: ...; barWidgetRegistry: ...; barConfig: ... }` properties are bound at declaration, satisfying the `required property` fields in `Bar.qml`'s root `Item` at construction time. A cloned bar instead loads via `pluginBarLoader`'s `Loader { source: shell.activeBarSourceUrl }` (async, URL-based) -- QML's declarative `Loader.source` has no way to supply initial property values, so the three `required property` fields are necessarily unset at construction, only assigned afterward via `configureBar`. Whatever depends on those properties being present *at construction* for a `PanelWindow`/layer-shell surface to map correctly seems to never recover once that happens.

## System details

- Omarchy version: `4.0.0-1`
- Kernel: `7.1.8-arch1-3`
- CPU: Intel (Alder Lake-S)
- GPU: Intel UHD 770 (i915) + NVIDIA GeForce RTX 5070 (`nvidia-open-dkms` 610.57.04)
- Bar position: `top`, default (non-cloned) bar otherwise working fine

## Workaround

None currently -- any customization that requires cloning the whole `bar` (rather than an individual `bar-widget`) hits this. Reverted to the stock `omarchy.bar` for now with `omarchy bar use omarchy.bar`.

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.