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 stop responding to mouse clicks
Reported by Rambo176 · 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
System details
ryzen 5600x with 3060 12 gb
What's wrong?
Problem
On Omarchy 4.0.2-1, some interactive top-bar widgets intermittently stop responding to mouse clicks.
I have observed this with:
- Dropbox
- Tailscale
- System Tray
- Agent Plugin
The icons remain visible, but clicking them sometimes does nothing.
The issue is temporarily fixed by either:
- restarting the Omarchy shell, or
- changing the bar position, which recreates the bar/widgets.
System
- Omarchy: 4.0.2-1
- Hyprland: 0.56.2
- GPU: NVIDIA RTX 3060
- NVIDIA driver: 610.57.04
- Wayland
Investigation
I performed a read-only investigation and found duplicate IpcHandler registrations for several built-in panel targets.
For example, shell/Ui/Panel.qml registers an IpcHandler using root.ipcTarget, while individual panels such as Dropbox and Tailscale also register an IpcHandler for the same target.
The journal reports warnings such as:
Handler was registered but will not be used because another handler is registered for target omarchy.dropbox
Similar duplicate-registration warnings were observed for multiple built-in targets, including Tailscale, Audio, Power, Monitor, Network, System Update, Weather, Clock, Indicators, and Agents.
The warnings also reappear during handler deregistration/re-registration cycles.
Changing the bar position causes the bar components to be recreated, and this consistently correlates with the widgets becoming clickable again.
Possible cause
The duplicate IpcHandler registrations may be related to the intermittent interaction failure, although I could not experimentally prove that they are definitively the root cause under a strict read-only investigation.
I therefore do not want to claim this as confirmed.
Expected behavior
Interactive top-bar widgets should continue accepting mouse clicks normally without requiring a shell restart or changing the bar position.
Question
Could the duplicate IpcHandler registrations in Ui/Panel.qml and the individual panel QML files be related to this intermittent click/input problem?
If not, could this be related to a Quickshell layer-shell, input-region, MouseArea/PointerHandler, or widget lifecycle issue?
I have intentionally left the shipped Omarchy QML files untouched and have not applied a local workaround.
View raw text
### System details ryzen 5600x with 3060 12 gb ### What's wrong? ## Problem On Omarchy 4.0.2-1, some interactive top-bar widgets intermittently stop responding to mouse clicks. I have observed this with: - Dropbox - Tailscale - System Tray - Agent Plugin The icons remain visible, but clicking them sometimes does nothing. The issue is temporarily fixed by either: - restarting the Omarchy shell, or - changing the bar position, which recreates the bar/widgets. ## System - Omarchy: 4.0.2-1 - Hyprland: 0.56.2 - GPU: NVIDIA RTX 3060 - NVIDIA driver: 610.57.04 - Wayland ## Investigation I performed a read-only investigation and found duplicate `IpcHandler` registrations for several built-in panel targets. For example, `shell/Ui/Panel.qml` registers an `IpcHandler` using `root.ipcTarget`, while individual panels such as Dropbox and Tailscale also register an `IpcHandler` for the same target. The journal reports warnings such as: `Handler was registered but will not be used because another handler is registered for target omarchy.dropbox` Similar duplicate-registration warnings were observed for multiple built-in targets, including Tailscale, Audio, Power, Monitor, Network, System Update, Weather, Clock, Indicators, and Agents. The warnings also reappear during handler deregistration/re-registration cycles. Changing the bar position causes the bar components to be recreated, and this consistently correlates with the widgets becoming clickable again. ## Possible cause The duplicate `IpcHandler` registrations may be related to the intermittent interaction failure, although I could not experimentally prove that they are definitively the root cause under a strict read-only investigation. I therefore do not want to claim this as confirmed. ## Expected behavior Interactive top-bar widgets should continue accepting mouse clicks normally without requiring a shell restart or changing the bar position. ## Question Could the duplicate `IpcHandler` registrations in `Ui/Panel.qml` and the individual panel QML files be related to this intermittent click/input problem? If not, could this be related to a Quickshell layer-shell, input-region, MouseArea/PointerHandler, or widget lifecycle issue? I have intentionally left the shipped Omarchy QML files untouched and have not applied a local workaround.
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:40 UTC