Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Cloned omarchy.bar cannot load as a bar option: required properties never initialized by pluginBarLoader
Reported by hshshshs12 · 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.
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
What happened
Cloning the stock bar and switching to the clone leaves the bar unable to load:
omarchy plugin clone omarchy.bar # creates <user>.bar and switches the bar to it
omarchy restart shellThe shell logs (quickshell log.qslog):
WARN scene: file://.../plugins/<user>.bar/Bar.qml[17:3]: Required property barWidgetRegistry was not initialized
WARN scene: file://.../plugins/<user>.bar/Bar.qml[15:3]: Required property omarchyPath was not initialized
WARN scene: file://.../plugins/<user>.bar/Bar.qml[22:3]: Required property barConfig was not initializedand the bar never appears.
Why
shell/plugins/bar/Bar.qml declares three host-injected properties as required property (lines 16, 18, 23 on master):
required property string omarchyPath
required property var barWidgetRegistry
required property var barConfigThat works for the built-in bar because defaultBarComponent in shell/shell.qml instantiates Bar with bindings. But a non-default bar option goes through pluginBarLoader (shell.qml ~line 248), which is a plain Loader with a source URL and assigns the properties only after instantiation, in onLoaded: shell.configureBar(item, ...). A Loader cannot instantiate a component whose required properties are unset, so the load fails with Loader.Error before configureBar ever runs.
Net effect: the stock bar works as the default, but a verbatim clone of it — the exact output of omarchy plugin clone omarchy.bar — can never load as a bar option.
Expected
A clone of the stock bar loads identically to the stock bar, so users can customize the bar engine the same way omarchy plugin clone supports for widgets.
Workaround
Edit the clone and convert the three required property declarations to plain properties with safe defaults ("" / null); configureBar assigns the real values right after load.
Aggravating factor
When the load fails, the intended fallback to the default bar also fails, leaving no bar at all — filed separately (see linked issue).
System
- Omarchy 4.0.1-1, Arch Linux (kernel 7.1.9-arch1-2)
- CPU: Intel i7-10700K, GPU: NVIDIA Quadro P2200
- Three 1920x1080 monitors
- Verified the same code is present on current master (
shell/plugins/bar/Bar.qmllines 16/18/23,shell/shell.qmlpluginBarLoader)
View raw text
### What happened Cloning the stock bar and switching to the clone leaves the bar unable to load: ``` omarchy plugin clone omarchy.bar # creates <user>.bar and switches the bar to it omarchy restart shell ``` The shell logs (quickshell `log.qslog`): ``` WARN scene: file://.../plugins/<user>.bar/Bar.qml[17:3]: Required property barWidgetRegistry was not initialized WARN scene: file://.../plugins/<user>.bar/Bar.qml[15:3]: Required property omarchyPath was not initialized WARN scene: file://.../plugins/<user>.bar/Bar.qml[22:3]: Required property barConfig was not initialized ``` and the bar never appears. ### Why `shell/plugins/bar/Bar.qml` declares three host-injected properties as `required property` (lines 16, 18, 23 on master): ```qml required property string omarchyPath required property var barWidgetRegistry required property var barConfig ``` That works for the built-in bar because `defaultBarComponent` in `shell/shell.qml` instantiates `Bar` with bindings. But a non-default bar option goes through `pluginBarLoader` (shell.qml ~line 248), which is a plain `Loader` with a `source` URL and assigns the properties only *after* instantiation, in `onLoaded: shell.configureBar(item, ...)`. A `Loader` cannot instantiate a component whose required properties are unset, so the load fails with `Loader.Error` before `configureBar` ever runs. Net effect: the stock bar works as the default, but a verbatim clone of it — the exact output of `omarchy plugin clone omarchy.bar` — can never load as a bar option. ### Expected A clone of the stock bar loads identically to the stock bar, so users can customize the bar engine the same way `omarchy plugin clone` supports for widgets. ### Workaround Edit the clone and convert the three `required property` declarations to plain properties with safe defaults (`""` / `null`); `configureBar` assigns the real values right after load. ### Aggravating factor When the load fails, the intended fallback to the default bar also fails, leaving no bar at all — filed separately (see linked issue). ### System - Omarchy 4.0.1-1, Arch Linux (kernel 7.1.9-arch1-2) - CPU: Intel i7-10700K, GPU: NVIDIA Quadro P2200 - Three 1920x1080 monitors - Verified the same code is present on current master (`shell/plugins/bar/Bar.qml` lines 16/18/23, `shell/shell.qml` `pluginBarLoader`)
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.