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.
Top-bar widgets intermittently become unclickable due to cross-PanelWindow hit-testing in moduleClickTargetAt()
Reported by Rambo176 · filed Sep 5, 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
System details
Ryzen 5600x with 3060ti with 32 gb of ram
What's wrong?
Top-bar widgets intermittently become unclickable
Description
Some Omarchy top-bar widgets intermittently stop responding to mouse clicks while remaining visually normal.
Affected widgets have included:
- Dropbox
- Tailscale
- System Tray
- Agents
- Audio / Speaker
The widgets remain visible in the correct position, but their effective click area can become displaced. In the attached screen recording, clicks may only work when the pointer is moved very close to the top edge.
Restarting the Omarchy shell or changing/repositioning the bar restores normal clicking.
Investigation
Initially, I suspected pointer delivery, overlay layers, duplicate IpcHandlers, bar geometry, or a Hyprland/Quickshell issue.
A read-only source audit instead identified a likely cross-PanelWindow hit-testing issue in:
/usr/share/omarchy/shell/plugins/bar/Bar.qml
Relevant code:
Bar.qml:101— sharedclickTargetsarrayBar.qml:966-976— separateBarPanel/PanelWindowinstances forQuickshell.screensBar.qml:1769— widgets receive the samebar: rootWidgetButton.qml:44-55— widgets register into the sharedclickTargetsBar.qml:762-782—moduleClickTargetAt()iterates the shared targets and calls:
slot.mapToItem(target, localX, localY)View raw text
### System details Ryzen 5600x with 3060ti with 32 gb of ram ### What's wrong? ## Top-bar widgets intermittently become unclickable ### Description Some Omarchy top-bar widgets intermittently stop responding to mouse clicks while remaining visually normal. Affected widgets have included: - Dropbox - Tailscale - System Tray - Agents - Audio / Speaker The widgets remain visible in the correct position, but their effective click area can become displaced. In the attached screen recording, clicks may only work when the pointer is moved very close to the top edge. Restarting the Omarchy shell or changing/repositioning the bar restores normal clicking. ### Investigation Initially, I suspected pointer delivery, overlay layers, duplicate `IpcHandler`s, bar geometry, or a Hyprland/Quickshell issue. A read-only source audit instead identified a likely cross-`PanelWindow` hit-testing issue in: `/usr/share/omarchy/shell/plugins/bar/Bar.qml` Relevant code: - `Bar.qml:101` — shared `clickTargets` array - `Bar.qml:966-976` — separate `BarPanel` / `PanelWindow` instances for `Quickshell.screens` - `Bar.qml:1769` — widgets receive the same `bar: root` - `WidgetButton.qml:44-55` — widgets register into the shared `clickTargets` - `Bar.qml:762-782` — `moduleClickTargetAt()` iterates the shared targets and calls: ```qml slot.mapToItem(target, localX, localY)
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:51 UTC