Proof Portal

Sign in
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-4802GitHub issuePublicReceived

Surface internal display defaults to 60 Hz when 120 Hz is available

Reported by Rohansguliani · filed Sep 1, 2026Closed upstream on 2026-09-01 by its own reporter Rohansguliani. GitHub close reason: completed. Closed by its own reporter — not by itself 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

Surface internal display defaults to 60 Hz when 120 Hz is availablerevision 1 · captured 2026-10-04 12:03 UTC via poll

System details

  • Microsoft Surface Pro 10 for Business
  • Intel Core Ultra 7 165U / Intel Meteor Lake-P graphics
  • Omarchy 4.0.2-1
  • Hyprland 0.56.2
  • linux-surface 6.19.8
  • Internal panel: 2880x1920, with 60 Hz and 120 Hz modes

What's wrong?

The default monitor rule uses mode = "preferred". On the Surface Pro 10 internal panel, the kernel exposes both native-resolution modes but marks/selects 60 Hz as preferred, so a default Omarchy session runs at 60 Hz:

Monitor eDP-1:
  [email protected]
  availableModes: [email protected] [email protected]

This makes scrolling and desktop animations feel noticeably less responsive than the panel's native 120 Hz capability.

Steps to reproduce

  1. Start Omarchy on a Surface Pro 10 with the default ~/.config/hypr/monitors.lua wildcard rule.
  2. Run hyprctl monitors all.
  3. Observe that eDP-1 is running at 60 Hz while the same native resolution is available at 120 Hz.

Expected behavior

On Surface hardware, Omarchy should select the highest refresh rate for the connected internal eDP panel while leaving external-monitor selection and explicit user monitor rules unchanged.

An explicit eDP-1 rule using Hyprland's highrr mode resolves the issue.

View raw text
### System details

- Microsoft Surface Pro 10 for Business
- Intel Core Ultra 7 165U / Intel Meteor Lake-P graphics
- Omarchy 4.0.2-1
- Hyprland 0.56.2
- `linux-surface` 6.19.8
- Internal panel: 2880x1920, with 60 Hz and 120 Hz modes

### What's wrong?

The default monitor rule uses `mode = "preferred"`. On the Surface Pro 10 internal panel, the kernel exposes both native-resolution modes but marks/selects 60 Hz as preferred, so a default Omarchy session runs at 60 Hz:

```text
Monitor eDP-1:
  [email protected]
  availableModes: [email protected] [email protected]
```

This makes scrolling and desktop animations feel noticeably less responsive than the panel's native 120 Hz capability.

### Steps to reproduce

1. Start Omarchy on a Surface Pro 10 with the default `~/.config/hypr/monitors.lua` wildcard rule.
2. Run `hyprctl monitors all`.
3. Observe that `eDP-1` is running at 60 Hz while the same native resolution is available at 120 Hz.

### Expected behavior

On Surface hardware, Omarchy should select the highest refresh rate for the connected internal eDP panel while leaving external-monitor selection and explicit user monitor rules unchanged.

An explicit `eDP-1` rule using Hyprland's `highrr` mode resolves the issue.

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.