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

Cloning the top-level bar plugin (omarchy.bar) breaks the bar on all monitors

Reported by Santym8 · filed Aug 30, 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 the top-level bar plugin (omarchy.bar) breaks the bar on all monitorsrevision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

omarchy plugin clone omarchy.bar produces a clone and switches to it, but the bar layer surface then fails to render on any monitor, even with zero edits to the cloned file.

Expected

Cloning omarchy.bar (per the documented "clone to customize" workflow) should produce a working, editable copy of the bar, same as cloning a bar-widget plugin (e.g. omarchy.workspaces) does.

Steps to reproduce

  1. omarchy plugin clone omarchy.bar
  2. omarchy restart shell
  3. hyprctl layers — no omarchy-bar namespace layer appears on any monitor.

No edits to the cloned Bar.qml are needed to reproduce this.

Root cause (found while investigating)

In shell.qml, the custom-bar path (pluginBarLoader, a Loader { source: ... }) instantiates the Bar component from a URL, then only assigns omarchyPath / barConfig / barWidgetRegistry afterward, in onLoaded: shell.configureBar(item, ...). But Bar.qml declares these three as required property. Required properties need to be supplied at construction time; assigning them after onLoaded is too late, so QML logs "Required property X was not initialized" for all three and the Bar component fails to instantiate correctly.

The default-bar path (defaultBarComponent) works fine because it binds these properties declaratively inline:

Component {
  id: defaultBarComponent
  Bar {
    omarchyPath: shell.omarchyPath
    barWidgetRegistry: shell.barWidgetRegistry
    barConfig: shell.barConfig
    shell: shell
    manifest: shell.barManifestFor(shell.defaultBarId)
  }
}

The custom-bar Loader path doesn't have an equivalent way to bind these before/at creation, since Loader.source (URL-based) instantiates the component immediately without support for passing initial required properties, unlike Loader.setSource(url, properties) or component.createObject(parent, properties).

Diagnostics

$ omarchy version
4.0.1-1
$ hyprctl version
Hyprland 0.56.2, commit efb50993780079460b0cbed1363e2166a2de1d9f
$ uname -r
7.1.9-arch1-2

journalctl at the moment of the failure:

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

(The last line is a secondary bug: pluginBarLoader.onStatusChanged calls errorString() as a bare function, but it's a method on the Loader item — should probably be pluginBarLoader.errorString() or similar, since as written it throws ReferenceError instead of logging the real load error.)

Workaround

omarchy plugin remove <clone-id> --yes restores omarchy.bar cleanly.

View raw text
## What happened

`omarchy plugin clone omarchy.bar` produces a clone and switches to it, but the bar layer surface then fails to render on **any** monitor, even with zero edits to the cloned file.

## Expected

Cloning `omarchy.bar` (per the documented "clone to customize" workflow) should produce a working, editable copy of the bar, same as cloning a bar-widget plugin (e.g. `omarchy.workspaces`) does.

## Steps to reproduce

1. `omarchy plugin clone omarchy.bar`
2. `omarchy restart shell`
3. `hyprctl layers` — no `omarchy-bar` namespace layer appears on any monitor.

No edits to the cloned `Bar.qml` are needed to reproduce this.

## Root cause (found while investigating)

In `shell.qml`, the custom-bar path (`pluginBarLoader`, a `Loader { source: ... }`) instantiates the `Bar` component from a URL, then only assigns `omarchyPath` / `barConfig` / `barWidgetRegistry` afterward, in `onLoaded: shell.configureBar(item, ...)`. But `Bar.qml` declares these three as `required property`. Required properties need to be supplied at construction time; assigning them after `onLoaded` is too late, so QML logs "Required property X was not initialized" for all three and the Bar component fails to instantiate correctly.

The default-bar path (`defaultBarComponent`) works fine because it binds these properties declaratively inline:

```qml
Component {
  id: defaultBarComponent
  Bar {
    omarchyPath: shell.omarchyPath
    barWidgetRegistry: shell.barWidgetRegistry
    barConfig: shell.barConfig
    shell: shell
    manifest: shell.barManifestFor(shell.defaultBarId)
  }
}
```

The custom-bar `Loader` path doesn't have an equivalent way to bind these before/at creation, since `Loader.source` (URL-based) instantiates the component immediately without support for passing initial required properties, unlike `Loader.setSource(url, properties)` or `component.createObject(parent, properties)`.

## Diagnostics

```
$ omarchy version
4.0.1-1
$ hyprctl version
Hyprland 0.56.2, commit efb50993780079460b0cbed1363e2166a2de1d9f
$ uname -r
7.1.9-arch1-2
```

journalctl at the moment of the failure:

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

(The last line is a secondary bug: `pluginBarLoader.onStatusChanged` calls `errorString()` as a bare function, but it's a method on the `Loader` item — should probably be `pluginBarLoader.errorString()` or similar, since as written it throws `ReferenceError` instead of logging the real load error.)

## Workaround

`omarchy plugin remove <clone-id> --yes` restores `omarchy.bar` cleanly.

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.