Proof Portal

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

Lock screen (hyprlock) doesn't fit screen when monitor scaling is applied

Reported by themarcelogaia · filed Jan 26, 2026Closed upstream on 2026-07-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

Lock screen (hyprlock) doesn't fit screen when monitor scaling is appliedrevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

AMD Ryzen 7 7800X3D, NVIDIA GeForce RTX 4090, Omarchy 3.3.3, Hyprland 0.53.1, Multi-monitor setup with mixed scaling (1.6x and 2x)

What's wrong?

Issue

The lock screen (hyprlock) applies monitor scaling settings from monitors.conf, causing the UI to become oversized and extend beyond the screen boundaries. Since the lock screen is fullscreen, it should ignore scaling and render at native resolution.

## Steps to reproduce
1. Set monitor scaling to 1.6x or 2x in ~/.config/hypr/monitors.conf:
monitor = DP-2, 3440x1440@175, 1080x480, 1.6
2. Lock the screen with Super + Ctrl + L or wait for auto-lock
3. Observe that the lock screen UI is too large and doesn't fit within the screen
4. It might not be apparent on a landscape monitor, but it's obvious at portrait orientation (see image). At regular scale the "Omarchy" text fits the screen even on portrait mode.

## Expected behavior
The lock screen should ignore monitor scaling settings and render at 1:1 scale since it's a fullscreen overlay. Scaling is meant for desktop UI elements, not fullscreen surfaces.

## Current workaround
None known - parts of the lock

!Image

screen UI are cut off on scaled displays.

View raw text

### System details

AMD Ryzen 7 7800X3D, NVIDIA GeForce RTX 4090, Omarchy 3.3.3, Hyprland 0.53.1, Multi-monitor setup with mixed scaling (1.6x and 2x)

### What's wrong?

## Issue
  The lock screen (hyprlock) applies monitor scaling settings from `monitors.conf`, causing the UI to become oversized and extend beyond the screen boundaries. Since the lock screen is fullscreen, it should ignore scaling and render at native resolution.

  ## Steps to reproduce
  1. Set monitor scaling to 1.6x or 2x in `~/.config/hypr/monitors.conf`:
     monitor = DP-2, 3440x1440@175, 1080x480, 1.6
  2. Lock the screen with `Super + Ctrl + L` or wait for auto-lock
  3. Observe that the lock screen UI is too large and doesn't fit within the screen
  4. It might not be apparent on a landscape monitor, but it's obvious at portrait orientation (see image). At regular scale the "Omarchy" text fits the screen even on portrait mode.

  ## Expected behavior
  The lock screen should ignore monitor scaling settings and render at 1:1 scale since it's a fullscreen overlay. Scaling is meant for desktop UI elements, not fullscreen surfaces.

  ## Current workaround
  None known - parts of the lock

![Image](https://github.com/user-attachments/assets/64041c43-d45e-40dd-b522-72c6f3a4312f)

 screen UI are cut off on scaled displays.

Image

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.

Proof

History & reports

Reference