Proof Portal

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-4889GitHub issuePublicReceived

Update: Agent and Speaker widgets also become unresponsive

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.

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

Update: Agent and Speaker widgets also become unresponsiverevision 1 · captured 2026-10-04 12:10 UTC via poll

System details

Ryzen 5600 x with nvidia 3060ti and ram is 32 gb

What's wrong?

Update: More top-bar widgets become unresponsive

I recorded a screen recording showing the issue.

The problem is not limited to Dropbox, Tailscale, or System Tray. I have also observed the same behavior with the Agents and Speaker/Audio widgets.

When the issue occurs:

  • The widget/icon remains visible and looks completely normal.
  • Clicking the widget does nothing.
  • There is no visible response from the widget.
  • The rest of the desktop continues to work normally.
  • Restarting the Omarchy shell restores the widget interactions.
  • The issue is intermittent. The widgets work normally after restarting the shell, but may become unresponsive again later.

The attached screen recording demonstrates the behavior.

Previous issue

I originally reported this problem in #10030:

#10030 — Top-bar widgets intermittently stop responding to mouse clicks

This update provides additional evidence and confirms that the issue can also affect the Agents and Speaker/Audio widgets.

Diagnostics requested by the developer

Following the investigation in #10122, I was asked to capture the compositor state before restarting the shell or changing the bar position.

I performed the requested diagnostics.

At the time of the diagnostic capture, the system was behaving normally.

hyprctl layers showed:

  • omarchy-background at the background layer
  • omarchy-bar at the top layer
  • Bar geometry: xywh: 0 0 1920 26
  • No mapped overlay layer
  • No omarchy-keyboard-panel
  • No omarchy-keyboard-panel-dismiss

Monitor state:

HDMI-A-2
1920x1080
scale: 1
reserved: [0, 26, 0, 0]
View raw text
### System details

Ryzen 5600 x with nvidia 3060ti and ram is 32 gb 

### What's wrong?

### Update: More top-bar widgets become unresponsive

I recorded a screen recording showing the issue.

The problem is not limited to Dropbox, Tailscale, or System Tray. I have also observed the same behavior with the **Agents** and **Speaker/Audio** widgets.

When the issue occurs:

- The widget/icon remains visible and looks completely normal.
- Clicking the widget does nothing.
- There is no visible response from the widget.
- The rest of the desktop continues to work normally.
- Restarting the Omarchy shell restores the widget interactions.
- The issue is intermittent. The widgets work normally after restarting the shell, but may become unresponsive again later.

The attached screen recording demonstrates the behavior.

### Previous issue

I originally reported this problem in **#10030**:

**#10030 — Top-bar widgets intermittently stop responding to mouse clicks**

This update provides additional evidence and confirms that the issue can also affect the **Agents** and **Speaker/Audio** widgets.

### Diagnostics requested by the developer

Following the investigation in **#10122**, I was asked to capture the compositor state before restarting the shell or changing the bar position.

I performed the requested [diagnostics.](url)

At the time of the diagnostic capture, the system was behaving normally.

`hyprctl layers` showed:

- `omarchy-background` at the background layer
- `omarchy-bar` at the top layer
- Bar geometry: `xywh: 0 0 1920 26`
- No mapped overlay layer
- No `omarchy-keyboard-panel`
- No `omarchy-keyboard-panel-dismiss`

Monitor state:

```text
HDMI-A-2
1920x1080
scale: 1
reserved: [0, 26, 0, 0]

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.