Proof Portal

Sign in
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-4878GitHub issuePublicReceived

Omarchy Top-Bar Intermittent Mouse Click Failure — Forensic Investigation Report

Reported by Rambo176 · filed Sep 4, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #10030 (R-1008). GitHub close reason: completed.

Open at source
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

Omarchy Top-Bar Intermittent Mouse Click Failure — Forensic Investigation Reportrevision 1 · captured 2026-10-04 12:10 UTC via poll

System details

Ryzen 5600x, Nvidia 3060 12gb, with 32 gb of ram

What's wrong?

We investigated this issue earlier and found that the problem is intermittent: the top-bar widgets can remain visible while their mouse clicks stop working. Restarting the Omarchy shell or changing the bar position restores the functionality.

I rechecked the status bar and Quickshell implementation more closely, and found another possible cause that seems worth investigating.

The current suspicion is related to the lifecycle of ModuleList / ModuleSlot instances.

The bar can rebuild/recreate its modules when the configuration or bar position changes. The center section also has anchored and unanchored module arrangements. During these transitions, it seems possible that an older module instance, ModuleSlot, or related QML input object could remain alive after the new instance has been created.

If that happens, the visible widget could still be rendered normally, while an old/stale QML object or input region is still present and affecting pointer events. This could explain the specific behavior we are seeing: the widget is visible and appears normal, but clicking it does nothing.

There is also a relevant comment in BarModel.js concerning hidden module lists and preventing them from constructing modules. The center-section handling of anchored/unanchored ModuleList instances therefore seems particularly worth checking.

Another important clue is that changing the bar position fixes the problem immediately. This causes the bar/module structure to be rebuilt. Restarting the Omarchy shell also fixes it, which completely recreates the Quickshell object tree. Both actions effectively recreate the modules and clear the broken click state.

I also rechecked the previous duplicate IpcHandler theory. I could not find duplicate fixed-target IPC registrations, so I don't think duplicate IPC registration is the cause.

Could you please check whether ModuleList / ModuleSlot instances or their associated mouse/input regions can survive a module/bar rebuild, particularly around the center section's anchored and unanchored module handling?

The main thing I'm wondering is whether a stale module instance or invisible input region could remain after a rebuild and interfere with mouse events on the newly created visible **widget.

View raw text
### System details

Ryzen 5600x, Nvidia 3060 12gb, with 32 gb of ram 

### What's wrong?

We investigated this issue earlier and found that the problem is intermittent: the top-bar widgets can remain visible while their mouse clicks stop working. Restarting the Omarchy shell or changing the bar position restores the functionality.

I rechecked the status bar and Quickshell implementation more closely, and found another possible cause that seems worth investigating.

The current suspicion is related to the lifecycle of ModuleList / ModuleSlot instances.

The bar can rebuild/recreate its modules when the configuration or bar position changes. The center section also has anchored and unanchored module arrangements. During these transitions, it seems possible that an older module instance, ModuleSlot, or related QML input object could remain alive after the new instance has been created.

If that happens, the visible widget could still be rendered normally, while an old/stale QML object or input region is still present and affecting pointer events. This could explain the specific behavior we are seeing: the widget is visible and appears normal, but clicking it does nothing.

There is also a relevant comment in BarModel.js concerning hidden module lists and preventing them from constructing modules. The center-section handling of anchored/unanchored ModuleList instances therefore seems particularly worth checking.

Another important clue is that changing the bar position fixes the problem immediately. This causes the bar/module structure to be rebuilt. Restarting the Omarchy shell also fixes it, which completely recreates the Quickshell object tree. Both actions effectively recreate the modules and clear the broken click state.

I also rechecked the previous duplicate IpcHandler theory. I could not find duplicate fixed-target IPC registrations, so I don't think duplicate IPC registration is the cause.

Could you please check whether ModuleList / ModuleSlot instances or their associated mouse/input regions can survive a module/bar rebuild, particularly around the center section's anchored and unanchored module handling?

The main thing I'm wondering is whether a stale module instance or invisible input region could remain after a rebuild and interfere with mouse events on the newly created visible **widget.

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.