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

Quickshell panels do not dismiss on outside clicks on another monitor

Reported by Xclipsen · filed Jul 31, 2026Closed upstream on 2026-08-01 by the merge of PR #6487 (closed by dhh). 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

Quickshell panels do not dismiss on outside clicks on another monitorrevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

  • Omarchy Quattro Dev 4.0.0.r1472.g283276b-1 (283276bec09a2bc17d8941071037e971c7423fd5)
  • Quickshell 0.3.0.r18.g10b439f-3 (10b439fc6e3fd65c15fe1c486271b31da05ed023)
  • Hyprland, multi-monitor setup

What's wrong?

Quickshell control panels opened from the bar do not dismiss when clicking outside the panel on a different monitor. Outside-click dismissal only works on the monitor where the panel was opened.

Steps to reproduce

  1. Use a setup with at least two monitors and a bar on each monitor.
  2. Open a bar panel such as Audio, Network, Bluetooth, Display, or Power on monitor A.
  3. Move the pointer to monitor B.
  4. Click an application or empty area on monitor B.

Actual behavior

The panel on monitor A remains open.

Clicking the same logical bar widget on monitor B has a related problem: the first click opens monitor B's local widget instance and transfers the global popout ownership instead of toggling the already-open logical panel closed. The panel therefore moves/reopens on monitor B rather than dismissing.

Expected behavior

An outside click on any monitor should dismiss the open panel. Clicking the same logical widget on another monitor should also act as a global toggle and close it.

Suspected cause

KeyboardPanel.qml creates a full-screen dismissal surface only on the anchor widget's screen (screen: anchorWindow ? anchorWindow.screen : null). Its MouseArea can consequently catch outside clicks only on that screen:

There is also one global activePopout, while every monitor has separate widget instances and separate local opened state. Popout ownership is compared by QML object identity, so the same plugin on another monitor is treated as a different owner:

This appears to be an Omarchy shell multi-monitor coordination issue rather than a user configuration problem.

View raw text
### System details

- Omarchy Quattro Dev `4.0.0.r1472.g283276b-1` (`283276bec09a2bc17d8941071037e971c7423fd5`)
- Quickshell `0.3.0.r18.g10b439f-3` (`10b439fc6e3fd65c15fe1c486271b31da05ed023`)
- Hyprland, multi-monitor setup

### What's wrong?

Quickshell control panels opened from the bar do not dismiss when clicking outside the panel on a different monitor. Outside-click dismissal only works on the monitor where the panel was opened.

#### Steps to reproduce

1. Use a setup with at least two monitors and a bar on each monitor.
2. Open a bar panel such as Audio, Network, Bluetooth, Display, or Power on monitor A.
3. Move the pointer to monitor B.
4. Click an application or empty area on monitor B.

#### Actual behavior

The panel on monitor A remains open.

Clicking the same logical bar widget on monitor B has a related problem: the first click opens monitor B's local widget instance and transfers the global popout ownership instead of toggling the already-open logical panel closed. The panel therefore moves/reopens on monitor B rather than dismissing.

#### Expected behavior

An outside click on any monitor should dismiss the open panel. Clicking the same logical widget on another monitor should also act as a global toggle and close it.

### Suspected cause

`KeyboardPanel.qml` creates a full-screen dismissal surface only on the anchor widget's screen (`screen: anchorWindow ? anchorWindow.screen : null`). Its `MouseArea` can consequently catch outside clicks only on that screen:

- [`shell/Ui/KeyboardPanel.qml#L59-L71`](https://github.com/basecamp/omarchy/blob/283276bec09a2bc17d8941071037e971c7423fd5/shell/Ui/KeyboardPanel.qml#L59-L71)
- [`shell/Ui/KeyboardPanel.qml#L235-L289`](https://github.com/basecamp/omarchy/blob/283276bec09a2bc17d8941071037e971c7423fd5/shell/Ui/KeyboardPanel.qml#L235-L289)

There is also one global `activePopout`, while every monitor has separate widget instances and separate local `opened` state. Popout ownership is compared by QML object identity, so the same plugin on another monitor is treated as a different owner:

- [`shell/plugins/bar/Bar.qml#L75`](https://github.com/basecamp/omarchy/blob/283276bec09a2bc17d8941071037e971c7423fd5/shell/plugins/bar/Bar.qml#L75)
- [`shell/plugins/bar/Bar.qml#L308-L319`](https://github.com/basecamp/omarchy/blob/283276bec09a2bc17d8941071037e971c7423fd5/shell/plugins/bar/Bar.qml#L308-L319)
- [`shell/plugins/bar/Bar.qml#L416-L427`](https://github.com/basecamp/omarchy/blob/283276bec09a2bc17d8941071037e971c7423fd5/shell/plugins/bar/Bar.qml#L416-L427)
- [`shell/Ui/Panel.qml#L21-L31`](https://github.com/basecamp/omarchy/blob/283276bec09a2bc17d8941071037e971c7423fd5/shell/Ui/Panel.qml#L21-L31)

This appears to be an Omarchy shell multi-monitor coordination issue rather than a user configuration problem.

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.