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 panel: first scale pill's left border disappears at fractional display scale
Reported by emindashdamirov11-lang · filed Sep 19, 2026Closed upstream on 2026-09-19 by its own reporter emindashdamirov11-lang. 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
Summary
In the monitor/display panel (omarchy.monitor), the left border of the first scale preset pill (the 1x box) is invisible at certain shell text sizes. Reducing the text size a notch makes it reappear — the border is being rendered on subpixel boundaries and antialiased away.
Expected
All six scale preset pills render with a visible 1px border on all four sides, regardless of monitor scale or shell text size.
Actual
The first (leftmost) pill in the SCALE row has no visible left border at the default text size (14px). All other pills' borders render fine. Lowering the text size (e.g. omarchy display text size 12) makes the border appear.
Steps to reproduce
- On a display with a fractional output scale (here
eDP-1= 1.25), set the shell text size above default, e.g.omarchy display text size 14. - Open the monitor display panel (brightness/display bar icon → SCALE section).
- Look at the leftmost
1xpreset pill: its left border is not visible. - Run
omarchy display text size 12and re-open the panel — the pill's left border now renders.
Environment
- Omarchy 4.0.4-1 (OS VERSION_ID 4.0.4)
- Hyprland 0.56.2 (commit efb50993780079460b0cbed1363e2166a2de1d9f)
- CPU: AMD Ryzen 7 4800H · GPU: NVIDIA GeForce GTX 1650 Ti Mobile
- Monitor:
eDP-11920×1080,scale=1.25(fractional) - Shell text base-size: 14px (
~/.config/omarchy/shell.toml [font] base-size = 14)
Analysis
The shell layer surfaces render at the output's device-pixel ratio (1.25 here), so integer logical coordinates land on fractional device pixels. The scale pills' idle border is a 1px line at 40% alpha drawn with Rectangle.border on the item boundary; the first pill sits exactly on the content row's left edge, so its left border is split across ~1.25 device pixels at partial alpha and effectively vanishes. Larger text bases (14 → fontScale 1.1667) aggravate the subpixel misalignment; smaller sizes land nearer whole pixels and the border renders. Scaling the output to an integer (e.g. 2.0) also restores the border.
Relevant code: shell/Ui/Button.qml (idle border: normal-border-width default 1, normal-border-alpha 0.4) and shell/plugins/panels/monitor/Panel.qml (ScalePill row layout).
View raw text
## Summary In the monitor/display panel (`omarchy.monitor`), the left border of the first scale preset pill (the `1x` box) is invisible at certain shell text sizes. Reducing the text size a notch makes it reappear — the border is being rendered on subpixel boundaries and antialiased away. ## Expected All six scale preset pills render with a visible 1px border on all four sides, regardless of monitor scale or shell text size. ## Actual The first (leftmost) pill in the SCALE row has no visible left border at the default text size (14px). All other pills' borders render fine. Lowering the text size (e.g. `omarchy display text size 12`) makes the border appear. ## Steps to reproduce 1. On a display with a **fractional output scale** (here `eDP-1` = 1.25), set the shell text size above default, e.g. `omarchy display text size 14`. 2. Open the monitor display panel (brightness/display bar icon → SCALE section). 3. Look at the leftmost `1x` preset pill: its left border is not visible. 4. Run `omarchy display text size 12` and re-open the panel — the pill's left border now renders. ## Environment - Omarchy 4.0.4-1 (OS VERSION_ID 4.0.4) - Hyprland 0.56.2 (commit efb50993780079460b0cbed1363e2166a2de1d9f) - CPU: AMD Ryzen 7 4800H · GPU: NVIDIA GeForce GTX 1650 Ti Mobile - Monitor: `eDP-1` 1920×1080, `scale=1.25` (fractional) - Shell text base-size: 14px (`~/.config/omarchy/shell.toml [font] base-size = 14`) ## Analysis The shell layer surfaces render at the output's device-pixel ratio (1.25 here), so integer logical coordinates land on fractional device pixels. The scale pills' idle border is a 1px line at 40% alpha drawn with `Rectangle.border` on the item boundary; the first pill sits exactly on the content row's left edge, so its left border is split across ~1.25 device pixels at partial alpha and effectively vanishes. Larger text bases (14 → fontScale 1.1667) aggravate the subpixel misalignment; smaller sizes land nearer whole pixels and the border renders. Scaling the output to an integer (e.g. 2.0) also restores the border. Relevant code: `shell/Ui/Button.qml` (idle border: `normal-border-width` default 1, `normal-border-alpha` 0.4) and `shell/plugins/panels/monitor/Panel.qml` (ScalePill row layout).
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.