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

Unknown-1 DRM connector should be disabled by default on T2 Mac

Reported by viirak · filed Sep 17, 2026 · open at source

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

Unknown-1 DRM connector should be disabled by default on T2 Macrevision 1 · captured 2026-09-28 21:23 UTC via poll

Problem

On T2 MacBooks (MacBookPro16,1), i915 detects an additional DRM connector called Unknown-1 (3584x2240 at 1920x0) alongside the physical panel eDP-1 (3072x1920). Unknown-1 is a phantom/duplicate connector (DRM connector type 39 = Unknown) that extends the desktop beyond the physical screen.

This causes workspace rendering outside the viewport, mouse cursor going off-screen, and desktop layout confusion.

Current behavior

  • Unknown-1 is detected and active by default in Hyprland
  • Was invisible during DPMS-off (idle/lock) but became visible after Service.qml fix (dim-to-5% instead of DPMS-off)
  • Disabling via monitors.lua caused Hyprland crash in some cases

Expected behavior

Unknown-1 should be disabled by default in Omarchy's Hyprland configuration.

Proposed solution

Add to default monitors.lua:

hl.monitor({ output = "Unknown-1", disabled = true })

Alternatively, consider disabling via hyprctl keyword at runtime (from Service.qml or startup script), kernel parameter, or udev rule.

System info

  • Machine: MacBookPro16,1 (T2)
  • GPU: Intel UHD 630 (i915) + AMD Navi14 (card1, blacklisted)
  • Kernel: linux-t2
  • Hyprland: 0.56.2
  • Unknown-1: DRM connector type 39 (Unknown), connected, on card0 (i915)

See also

  • omarchy Discussion #773 (T2 Mac setup guide)
  • omarchy issue about lockscreen crash on wake
  • omarchy issue #4069 (GPU lockup, iGPU disable solved issues for some)
View raw text
## Problem

On T2 MacBooks (MacBookPro16,1), i915 detects an additional DRM connector called Unknown-1 (3584x2240 at 1920x0) alongside the physical panel eDP-1 (3072x1920). Unknown-1 is a phantom/duplicate connector (DRM connector type 39 = Unknown) that extends the desktop beyond the physical screen.

This causes workspace rendering outside the viewport, mouse cursor going off-screen, and desktop layout confusion.

## Current behavior

- Unknown-1 is detected and active by default in Hyprland
- Was invisible during DPMS-off (idle/lock) but became visible after Service.qml fix (dim-to-5% instead of DPMS-off)
- Disabling via monitors.lua caused Hyprland crash in some cases

## Expected behavior

Unknown-1 should be disabled by default in Omarchy's Hyprland configuration.

## Proposed solution

Add to default monitors.lua:
```lua
hl.monitor({ output = "Unknown-1", disabled = true })
```

Alternatively, consider disabling via hyprctl keyword at runtime (from Service.qml or startup script), kernel parameter, or udev rule.

## System info

- Machine: MacBookPro16,1 (T2)
- GPU: Intel UHD 630 (i915) + AMD Navi14 (card1, blacklisted)
- Kernel: linux-t2
- Hyprland: 0.56.2
- Unknown-1: DRM connector type 39 (Unknown), connected, on card0 (i915)

## See also

- omarchy Discussion #773 (T2 Mac setup guide)
- omarchy issue about lockscreen crash on wake
- omarchy issue #4069 (GPU lockup, iGPU disable solved issues for some)

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 14:48 UTC