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

DisplayPort audio ELD lost after S3 resume and lid transition while video remains connected

Reported by antipopp · filed Sep 27, 2026 · open at source

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

DisplayPort audio ELD lost after S3 resume and lid transition while video remains connectedrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

ThinkPad X1 Carbon Gen 10, Intel Core i7-1255U, Intel Iris Xe (i915), Intel SOF audio, LG UltraWide 3440×1440@160 Hz connected via USB-C/DisplayPort, Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy, Hyprland 0.56.2, PipeWire 1.6.8, WirePlumber 0.5.17

What's wrong?

After resuming the laptop from S3 suspend, the external monitor continues to display video but its audio output disappears from Omarchy's audio controls. Only the laptop speakers remain available.

This has happened twice. The second occurrence followed these steps:

  1. Suspend the laptop with the USB-C monitor connected.
  2. Leave it suspended for an extended period (about 15 hours in this occurrence).
  3. Open the lid to wake it and log in.
  4. Close the lid to use only the external monitor.
  5. Open the audio controls. The monitor output is missing and only the laptop speakers are available.

While broken:

  • DRM reported DP-3: connected, and video worked at 3440x1440@160 Hz.
  • All ALSA DisplayPort ELD endpoints reported monitor_present=0 and eld_valid=0.
  • PipeWire created the three HDMI/DisplayPort sinks but marked every corresponding port not available.
  • WirePlumber selected the laptop speaker profile/output.

Cycling DPMS for only the external display restored audio without rebooting or reconnecting USB-C:

hyprctl dispatch 'hl.dsp.dpms({ action = "disable", monitor = "DP-3" })'
sleep 3
hyprctl dispatch 'hl.dsp.dpms({ action = "enable", monitor = "DP-3" })'

Immediately afterward, ALSA reported:

monitor_present  1
eld_valid        1
monitor_name     LG ULTRAWIDE
connection_type  DisplayPort

The monitor output then reappeared and became the active PipeWire sink. A reboot also recovered the first occurrence.

Expected behavior: DisplayPort audio should be re-detected after resume and lid/display transitions, or Omarchy should retrigger the external display link when this state occurs.

Diagnostics were captured while the system was in the broken state, including omarchy-debug, wpctl status, pactl list cards, all ALSA ELD entries, DRM connector state, Hyprland monitor state, and the journal around resume.

omarchy-audio-report-2026-09-27-sanitized.tar.gz

View raw text
### System details

ThinkPad X1 Carbon Gen 10, Intel Core i7-1255U, Intel Iris Xe (i915), Intel SOF audio, LG UltraWide 3440×1440@160 Hz connected via USB-C/DisplayPort, Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy, Hyprland 0.56.2, PipeWire 1.6.8, WirePlumber 0.5.17

### What's wrong?

After resuming the laptop from S3 suspend, the external monitor continues to display video but its audio output disappears from Omarchy's audio controls. Only the laptop speakers remain available.

This has happened twice. The second occurrence followed these steps:

1. Suspend the laptop with the USB-C monitor connected.
2. Leave it suspended for an extended period (about 15 hours in this occurrence).
3. Open the lid to wake it and log in.
4. Close the lid to use only the external monitor.
5. Open the audio controls. The monitor output is missing and only the laptop speakers are available.

While broken:

- DRM reported `DP-3: connected`, and video worked at 3440x1440@160 Hz.
- All ALSA DisplayPort ELD endpoints reported `monitor_present=0` and `eld_valid=0`.
- PipeWire created the three HDMI/DisplayPort sinks but marked every corresponding port `not available`.
- WirePlumber selected the laptop speaker profile/output.

Cycling DPMS for only the external display restored audio without rebooting or reconnecting USB-C:

```sh
hyprctl dispatch 'hl.dsp.dpms({ action = "disable", monitor = "DP-3" })'
sleep 3
hyprctl dispatch 'hl.dsp.dpms({ action = "enable", monitor = "DP-3" })'
```

Immediately afterward, ALSA reported:

```text
monitor_present  1
eld_valid        1
monitor_name     LG ULTRAWIDE
connection_type  DisplayPort
```

The monitor output then reappeared and became the active PipeWire sink. A reboot also recovered the first occurrence.

Expected behavior: DisplayPort audio should be re-detected after resume and lid/display transitions, or Omarchy should retrigger the external display link when this state occurs.

Diagnostics were captured while the system was in the broken state, including `omarchy-debug`, `wpctl status`, `pactl list cards`, all ALSA ELD entries, DRM connector state, Hyprland monitor state, and the journal around resume.

[omarchy-audio-report-2026-09-27-sanitized.tar.gz](https://github.com/user-attachments/files/32696216/omarchy-audio-report-2026-09-27-sanitized.tar.gz)
  • omarchy-audio-report-2026-09-27-sanitized.tar.gz

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 19:05 UTC