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

Kernel hard-hangs on Steam Deck within ~0.7s of undocking USB-C dock (session and journal both die silently)

Reported by Amos-Huckleberry · filed Oct 12, 2026 · open at source

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

Kernel hard-hangs on Steam Deck within ~0.7s of undocking USB-C dock (session and journal both die silently)revision 1 · captured 2026-10-12 03:25 UTC via poll

Reported in #7228 (comment), where the panel-recovery part was confirmed and
triaged as covered by #7209. Per the triage note, this kernel hang on undock is
a separate failure and not covered by that report, so it gets its own issue.

System details

  • Device: Steam Deck (AMD Van Gogh APU, eDP-only internal panel), Hyprland desktop mode under uwsm
  • Omarchy: omarchy-dev 4.0.0.r1832.g23dab9e-1
  • Hyprland: 0.56.2
  • Kernel: 6.11.11-valve29-1-neptune-611-g2dcfaf4df7ac

What's wrong?

Physically undocking the USB-C dock hard-hangs the kernel within ~0.7s of the
disconnect event. No panic, no shutdown sequence: the journal simply stops.
The machine becomes unresponsive and requires a force power-off
(next boot began ~43s later).

Journal at the hang

Sep 22 19:56:44.380 kernel: usb 1-1: USB disconnect, device number 6
Sep 22 19:56:44.418 Telegram[9037]: There are no outputs - creating placeholder screen
Sep 22 19:56:45.103 omarchy-shell[4152]: INFO qt.qpa.wayland: There are no outputs - creating placeholder screen
Sep 22 19:56:45.105 kernel: r8152-cfgselector ...
<journal ends — no panic, no oops, no shutdown records; next boot starts ~43s later>

Steps to reproduce

  1. Steam Deck on Omarchy 4.x, running Hyprland desktop mode under uwsm, docked via USB-C
  2. Physically undock the USB-C cable from the Deck
  3. Within ~0.7s the session dies and the kernel hangs; force power-off required

Context / distinct from #7209

This predates the panel-toggle recovery guard: even a correct
omarchy-hyprland-monitor-internal recover() could not have run in this window,
because the compositor dropped to the placeholder-screen state and the kernel
stopped before anything could react. Practical impact on a handheld is
"screen dead, force power-off and reboot," not just a dark panel.

Panic/lockup sysctls are now enabled to try to capture a trace on the next
occurrence; will follow up with that output.

View raw text
Reported in #7228 (comment), where the panel-recovery part was confirmed and
triaged as covered by #7209. Per the triage note, this kernel hang on undock is
a separate failure and not covered by that report, so it gets its own issue.

### System details
- Device: Steam Deck (AMD Van Gogh APU, eDP-only internal panel), Hyprland desktop mode under uwsm
- Omarchy: omarchy-dev 4.0.0.r1832.g23dab9e-1
- Hyprland: 0.56.2
- Kernel: 6.11.11-valve29-1-neptune-611-g2dcfaf4df7ac

### What's wrong?
Physically undocking the USB-C dock hard-hangs the kernel within ~0.7s of the
disconnect event. No panic, no shutdown sequence: the journal simply stops.
The machine becomes unresponsive and requires a force power-off
(next boot began ~43s later).

### Journal at the hang
```
Sep 22 19:56:44.380 kernel: usb 1-1: USB disconnect, device number 6
Sep 22 19:56:44.418 Telegram[9037]: There are no outputs - creating placeholder screen
Sep 22 19:56:45.103 omarchy-shell[4152]: INFO qt.qpa.wayland: There are no outputs - creating placeholder screen
Sep 22 19:56:45.105 kernel: r8152-cfgselector ...
<journal ends — no panic, no oops, no shutdown records; next boot starts ~43s later>
```

### Steps to reproduce
1. Steam Deck on Omarchy 4.x, running Hyprland desktop mode under uwsm, docked via USB-C
2. Physically undock the USB-C cable from the Deck
3. Within ~0.7s the session dies and the kernel hangs; force power-off required

### Context / distinct from #7209
This predates the panel-toggle recovery guard: even a correct
`omarchy-hyprland-monitor-internal recover()` could not have run in this window,
because the compositor dropped to the placeholder-screen state and the kernel
stopped before anything could react. Practical impact on a handheld is
"screen dead, force power-off and reboot," not just a dark panel.

Panic/lockup sysctls are now enabled to try to capture a trace on the next
occurrence; will follow up with that output.

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-12 03:29 UTC