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.
Disable Internal (Laptop) Display on Lid Close
Reported by curtisspendlove · filed Jul 31, 2025Closed upstream on 2025-11-03 by dhh, as a duplicate of #427 (R-2389). GitHub close reason: not_planned.
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
My Framework 13 (2.8K Display upgrade) keeps the internal display awake even after the laptop lid is closed. This led to some fairly confusing behavior (including launching windows on the internal display--a LOT of them, since I just kept hitting the keybinds)
The following bindl directives have resolved this for me, in my testing it needs to be in hyprland.conf and not monitors.conf (binds? probably).
bindl=,switch:on:Lid Switch,exec,hyprctl keyword monitor "eDP-1, disable"
bindl=,switch:off:Lid Switch,exec,hyprctl keyword monitor "eDP-1, preferred, auto, auto"I would like assistance testing this as I only have a single data point:
Framework 13 (I'll edit with stats in a bit)
ASUS ProArt 5K Display
PLEASE try if you are experiencing this on any laptop and I'd love non-framework feedback as well. My theory is that this is a problem for all internal displays but I'm unsure.
Prospective PR (in a fork so I can clean it up before I push the branch to upstream): https://github.com/knightoftheoldcode/omarchy/pull/1
TIA!
Ref: #332
View raw text
My Framework 13 (2.8K Display upgrade) keeps the internal display awake even after the laptop lid is closed. This led to some fairly confusing behavior (including launching windows on the internal display--a LOT of them, since I just kept hitting the keybinds) The following `bindl` directives have resolved this for me, in my testing it needs to be in `hyprland.conf` and not `monitors.conf` (binds? probably). ``` bindl=,switch:on:Lid Switch,exec,hyprctl keyword monitor "eDP-1, disable" bindl=,switch:off:Lid Switch,exec,hyprctl keyword monitor "eDP-1, preferred, auto, auto" ``` I would like assistance testing this as I only have a single data point: Framework 13 (I'll edit with stats in a bit) ASUS ProArt 5K Display PLEASE try if you are experiencing this on any laptop and I'd love non-framework feedback as well. My theory is that this is a problem for all internal displays but I'm unsure. Prospective PR (in a fork so I can clean it up before I push the branch to upstream): https://github.com/knightoftheoldcode/omarchy/pull/1 TIA! Ref: #332
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.