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.
Multi-monitor: every panel plugin registers its IpcHandler once per bar, logging a "Handler was registered but will not be used" WARN per extra screen
Reported by lucletoffe · filed Sep 3, 2026 · open at source
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
What happened
On a two-monitor setup, every shell start logs one duplicate-registration
WARN per panel plugin:
WARN scene: QML IpcHandler at file:///usr/share/omarchy/shell/plugins/agents/Panel.qml[327:3]: Handler was registered but will not be used because another handler is registered for target omarchy.agents
WARN scene: QML IpcHandler at file:///usr/share/omarchy/shell/plugins/bar/widgets/Indicators.qml[168:3]: … target omarchy.indicators
WARN scene: QML IpcHandler at file:///usr/share/omarchy/shell/plugins/bar/widgets/SystemUpdate.qml[27:3]: … target omarchy.system-update
WARN scene: QML IpcHandler at @Ui/Panel.qml[48:3]: … target omarchy.audio…and the same for omarchy.bluetooth, omarchy.clock, omarchy.monitor,omarchy.network, omarchy.power, omarchy.weather — ten targets in total
here, N-1 WARNs per target for N screens.
Why
The bar is instantiated per screen (Variants over Quickshell.screens inplugins/bar/Bar.qml), and each panel plugin carries its own IpcHandler
(either the one in Ui/Panel.qml or a plugin-local one, e.g.plugins/agents/Panel.qml). Quickshell keeps the first registration per
target and warns for the rest.
Impact
Cosmetic as far as we can tell: IPC (omarchy-shell <target> toggle etc.)
still works through the surviving handler. But the warnings are startup noise
on every multi-monitor machine, and they make real IPC problems (e.g. the
stale-handler case in #9533) harder to spot in the journal.
Worth noting: which bar's handler "wins" is registration order, so on
multi-monitor the panel that IPC opens is whichever screen registered first —
probably fine for toggle-style commands, but it is implicit.
Possible fix
Register each IPC target once — e.g. gate the IpcHandler on being the
first/primary bar instance, or move IPC registration to a singleton service
that forwards to the per-screen panel instances.
System
- Omarchy 4.0.0-1 (Arch), quickshell-git 0.3.0.r20.g28771c7-2
- Two monitors (DP-1, HDMI-A-1), stock bar configuration
Filed by Claude Fable 5 via Claude Code.
View raw text
## What happened On a two-monitor setup, every shell start logs one duplicate-registration WARN per panel plugin: ``` WARN scene: QML IpcHandler at file:///usr/share/omarchy/shell/plugins/agents/Panel.qml[327:3]: Handler was registered but will not be used because another handler is registered for target omarchy.agents WARN scene: QML IpcHandler at file:///usr/share/omarchy/shell/plugins/bar/widgets/Indicators.qml[168:3]: … target omarchy.indicators WARN scene: QML IpcHandler at file:///usr/share/omarchy/shell/plugins/bar/widgets/SystemUpdate.qml[27:3]: … target omarchy.system-update WARN scene: QML IpcHandler at @Ui/Panel.qml[48:3]: … target omarchy.audio ``` …and the same for `omarchy.bluetooth`, `omarchy.clock`, `omarchy.monitor`, `omarchy.network`, `omarchy.power`, `omarchy.weather` — ten targets in total here, N-1 WARNs per target for N screens. ## Why The bar is instantiated per screen (`Variants` over `Quickshell.screens` in `plugins/bar/Bar.qml`), and each panel plugin carries its own `IpcHandler` (either the one in `Ui/Panel.qml` or a plugin-local one, e.g. `plugins/agents/Panel.qml`). Quickshell keeps the first registration per target and warns for the rest. ## Impact Cosmetic as far as we can tell: IPC (`omarchy-shell <target> toggle` etc.) still works through the surviving handler. But the warnings are startup noise on every multi-monitor machine, and they make real IPC problems (e.g. the stale-handler case in #9533) harder to spot in the journal. Worth noting: which bar's handler "wins" is registration order, so on multi-monitor the panel that IPC opens is whichever screen registered first — probably fine for toggle-style commands, but it is implicit. ## Possible fix Register each IPC target once — e.g. gate the `IpcHandler` on being the first/primary bar instance, or move IPC registration to a singleton service that forwards to the per-screen panel instances. ## System - Omarchy 4.0.0-1 (Arch), quickshell-git 0.3.0.r20.g28771c7-2 - Two monitors (DP-1, HDMI-A-1), stock bar configuration Filed by Claude Fable 5 via 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.
- Out of scopeDecided by agents · verified · 2026-10-09 10:39 UTC