Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Monitor scale cycling crashes on non-standard resolutions (1366x768, etc.)
Reported by meirdick · filed Mar 15, 2026Closed upstream on 2026-08-07 by its own reporter meirdick. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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
Problem
omarchy-hyprland-monitor-scaling-cycle (bound to Super+/) hardcodes the scale cycle 1 → 1.6 → 2 → 3 → 1. On displays where these scales don't divide cleanly into the native resolution, Hyprland shows an error:
Invalid scale passed to monitor eDP-1, failed to find a clean divisor Hyprland may not work correctly
Affected resolutions
| Resolution | Broken scales |
|---|---|
| 1366x768 | 1.6 (853.75 width), 3 (455.33 width) |
| 2560x1440 | 3 (853.33 width) |
| 6016x3384 | 3 (2005.33 width) |
1366x768 is common on budget laptops and older displays. 2560x1440 is one of the most popular monitor resolutions. Both hit this issue.
Steps to reproduce
- Have a 1366x768 display (or 2560x1440)
- Press Super+/ to cycle monitor scaling
- Hyprland shows the "Invalid scale" error bar across the top of the screen
Proposed fix
Before applying a scale, validate that it produces integer pixel dimensions (width/scale and height/scale are both whole numbers). Skip invalid scales and cycle to the next valid one. If only scale 1x is valid, show a notification instead of cycling.
This preserves existing behavior for displays that support all scales (1920x1080, 2880x1920, 3840x2160) and gracefully handles the rest.
View raw text
## Problem `omarchy-hyprland-monitor-scaling-cycle` (bound to Super+/) hardcodes the scale cycle `1 → 1.6 → 2 → 3 → 1`. On displays where these scales don't divide cleanly into the native resolution, Hyprland shows an error: > Invalid scale passed to monitor eDP-1, failed to find a clean divisor > Hyprland may not work correctly ### Affected resolutions | Resolution | Broken scales | |---|---| | 1366x768 | 1.6 (853.75 width), 3 (455.33 width) | | 2560x1440 | 3 (853.33 width) | | 6016x3384 | 3 (2005.33 width) | 1366x768 is common on budget laptops and older displays. 2560x1440 is one of the most popular monitor resolutions. Both hit this issue. ### Steps to reproduce 1. Have a 1366x768 display (or 2560x1440) 2. Press Super+/ to cycle monitor scaling 3. Hyprland shows the "Invalid scale" error bar across the top of the screen ## Proposed fix Before applying a scale, validate that it produces integer pixel dimensions (`width/scale` and `height/scale` are both whole numbers). Skip invalid scales and cycle to the next valid one. If only scale 1x is valid, show a notification instead of cycling. This preserves existing behavior for displays that support all scales (1920x1080, 2880x1920, 3840x2160) and gracefully handles the rest.
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.