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-2190GitHub issuePublicDecided· Out of scope

Hidden bar still captures clicks over a fullscreen window

Reported by karacas · filed Oct 2, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

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

Hidden bar still captures clicks over a fullscreen windowrevision 1 · captured 2026-10-02 20:13 UTC via poll

System details

AMD Ryzen 5 5500, NVIDIA GTX 1660 SUPER, Omarchy 4.0.4-1, Hyprland 0.56.2

What's wrong?

When a window is fullscreen (SUPER + F), the top ~40px of the screen (where the bar normally sits) don't pass clicks through to the fullscreen app. The bar is hidden behind the fullscreen window, but it still receives pointer input.

Steps to reproduce

  1. Open any app (e.g. a terminal or browser) and press SUPER + F.
  2. Click on something in the top strip of the app, where the bar would be (e.g. the browser tab strip).
  3. The app doesn't get the click. The bar widget under the pointer reacts instead. Clicking where the clock sits opens the calendar panel over the fullscreen app (see screenshot).

Expected: while a window is fullscreen and the bar is hidden behind it, clicks in that area go to the fullscreen window.

Notes

  • hyprctl layers shows the bar as namespace: omarchy-bar on layer level 2 (top), 0 0 2752 40.
  • Possibly related: default/hypr/apps/omarchy-shell.lua sets no_anim = true, animation = "none" on the omarchy-bar layer. Hyprland hides top layers under fullscreen by fading their alpha out and skips alpha-0 layers in input hit-testing. If the bar's alpha never reaches 0, it would stay invisible but keep taking input. This is a hypothesis, not verified.
View raw text
### System details

AMD Ryzen 5 5500, NVIDIA GTX 1660 SUPER, Omarchy 4.0.4-1, Hyprland 0.56.2

### What's wrong?

When a window is fullscreen (`SUPER + F`), the top ~40px of the screen (where the bar normally sits) don't pass clicks through to the fullscreen app. The bar is hidden behind the fullscreen window, but it still receives pointer input.

**Steps to reproduce**

1. Open any app (e.g. a terminal or browser) and press `SUPER + F`.
2. Click on something in the top strip of the app, where the bar would be (e.g. the browser tab strip).
3. The app doesn't get the click. The bar widget under the pointer reacts instead. Clicking where the clock sits opens the calendar panel over the fullscreen app (see screenshot).

**Expected:** while a window is fullscreen and the bar is hidden behind it, clicks in that area go to the fullscreen window.

**Notes**

- `hyprctl layers` shows the bar as `namespace: omarchy-bar` on layer level 2 (top), `0 0 2752 40`.
- Possibly related: `default/hypr/apps/omarchy-shell.lua` sets `no_anim = true, animation = "none"` on the `omarchy-bar` layer. Hyprland hides top layers under fullscreen by fading their alpha out and skips alpha-0 layers in input hit-testing. If the bar's alpha never reaches 0, it would stay invisible but keep taking input. This is a hypothesis, not verified.

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 20:47 UTC