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

Workspace bar widget highlights the same workspace on all monitors instead of each monitor's own active workspace

Reported by cjoprey · filed Sep 7, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #8183 (R-1479). 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

Workspace bar widget highlights the same workspace on all monitors instead of each monitor's own active workspacerevision 1 · captured 2026-10-04 12:10 UTC via poll

What happened

On a two-monitor setup, the workspace indicator widget in the bar (omarchy.workspaces) highlights the same workspace number as "active" on both monitors' bars, even though each monitor is genuinely displaying a different workspace.

Steps to reproduce

  1. Use two monitors, each showing a different workspace (e.g. workspace 1 on the primary monitor, workspace 2 on the secondary monitor).
  2. Observe the bar's workspace widget on each monitor.
  3. Press SUPER+<N> to switch to a workspace already displayed on the other monitor (Hyprland's global workspace dispatcher just moves focus to that monitor instead of moving windows — this part is expected Hyprland behavior).
  4. Notice that both bars now highlight workspace <N> as "focused", even though only one monitor is actually showing/using it.

Expected behavior

Each monitor's bar should highlight whichever workspace is actually active/displayed on that monitor, not a single globally-focused workspace shared across all bars.

Root cause (found in source)

In shell/plugins/bar/widgets/Workspaces.qml:

readonly property bool focused: Hyprland.focusedWorkspace !== null && Hyprland.focusedWorkspace.id === modelData

Hyprland.focusedWorkspace is a single global property representing the workspace of whichever monitor currently has keyboard focus. Since the bar is instantiated once per monitor (per the comment in shell/Ui/BarWidget.qml), each bar instance evaluates this same global value, so all bars highlight the same workspace number regardless of which workspace is actually shown on that particular monitor.

The fix should compare against that widget instance's own monitor's active workspace (e.g. via the monitor associated with the bar surface) instead of the global Hyprland.focusedWorkspace.

System details

  • Omarchy version: 4.0.2-1
  • Setup: two monitors (eDP-1 laptop panel + DP-5 external), configured in ~/.config/hypr/monitors.lua
View raw text
## What happened

On a two-monitor setup, the workspace indicator widget in the bar (`omarchy.workspaces`) highlights the **same workspace number as "active" on both monitors' bars**, even though each monitor is genuinely displaying a different workspace.

### Steps to reproduce
1. Use two monitors, each showing a different workspace (e.g. workspace 1 on the primary monitor, workspace 2 on the secondary monitor).
2. Observe the bar's workspace widget on each monitor.
3. Press `SUPER+<N>` to switch to a workspace already displayed on the *other* monitor (Hyprland's global `workspace` dispatcher just moves focus to that monitor instead of moving windows — this part is expected Hyprland behavior).
4. Notice that **both** bars now highlight workspace `<N>` as "focused", even though only one monitor is actually showing/using it.

### Expected behavior
Each monitor's bar should highlight whichever workspace is actually active/displayed **on that monitor**, not a single globally-focused workspace shared across all bars.

### Root cause (found in source)
In `shell/plugins/bar/widgets/Workspaces.qml`:

```qml
readonly property bool focused: Hyprland.focusedWorkspace !== null && Hyprland.focusedWorkspace.id === modelData
```

`Hyprland.focusedWorkspace` is a single global property representing the workspace of whichever monitor currently has keyboard focus. Since the bar is instantiated once per monitor (per the comment in `shell/Ui/BarWidget.qml`), each bar instance evaluates this same global value, so all bars highlight the same workspace number regardless of which workspace is actually shown on that particular monitor.

The fix should compare against that widget instance's own monitor's active workspace (e.g. via the monitor associated with the bar surface) instead of the global `Hyprland.focusedWorkspace`.

## System details
- Omarchy version: 4.0.2-1
- Setup: two monitors (`eDP-1` laptop panel + `DP-5` external), configured in `~/.config/hypr/monitors.lua`

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.