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

External Monitors using monitors.lua lack of consistancy

Reported by YuseiRun · filed Aug 22, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 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

External Monitors using monitors.lua lack of consistancyrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

Omarchy 4

What's wrong?

I am unable to properly test the failures do to the inconsistancy, but I will record what I did to put me in my current position.
- I updated to Omarchy 4
- Monitors had no issues
- I changed the lockscreen to be consistent with my theme
- I rebooted the computer
- The screen now has black bars on the sides
- I change the gdk scale and nothing happens
- I change the monitor scale and the change is reflected in the display (however on reboot my screen scale looks different"
- I had changed output="" to output="auto" and did not like the change and when I reverted the change, it was not what it was originally
- The mode and position I found using hyprctl monitors (I say that this shouldnt be the problem"
- Below is my current config

below is my current monitors.lua config

local omarchy_gdk_scale = 1
local omarchy_monitor_scale = 1


hl.env("GDK_SCALE", tostring(omarchy_gdk_scale))
hl.monitor({ output = "", mode = "1024x768@60" , position = "0x0", scale = omarchy_monitor_scale })

This issue only came with the Omarchy 4 update

View raw text
### System details

Omarchy 4

### What's wrong?

I am unable to properly test the failures do to the inconsistancy, but I will record what I did to put me in my current position.
- I updated to Omarchy 4
- Monitors had no issues
- I changed the lockscreen to be consistent with my theme
- I rebooted the computer
- The screen now has black bars on the sides
- I change the gdk scale and nothing happens
- I change the monitor scale and the change is reflected in the display (however on reboot my screen scale looks different"
- I had changed `output=""` to  `output="auto"` and did not like the change and when I reverted the change, it was not what it was originally
- The mode and position I found using `hyprctl monitors` (I say that this shouldnt be the problem"
- Below is my current config 



below is my current monitors.lua config
```
local omarchy_gdk_scale = 1
local omarchy_monitor_scale = 1


hl.env("GDK_SCALE", tostring(omarchy_gdk_scale))
hl.monitor({ output = "", mode = "1024x768@60" , position = "0x0", scale = omarchy_monitor_scale })

```


This issue only came with the Omarchy 4 update

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 08:23 UTC