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-1696GitHub issuePublicReceived

hyprlock died because streamwebhelper

Reported by wandyirawan · filed Aug 18, 2026 · open at source

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

hyprlock died because streamwebhelperrevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

amd rx6600, ryzen 5600g, omarchy v4

What's wrong?

Crash Report: steamwebhelper PID 4073892
What crashed and what it was doing
steamwebhelper (Valve's embedded Chromium browser for Steam) died with SIGBUS (BUS_ADRERR) while running a memory copy in V_memcpy_nocache inside Valve's libvstdlib_s.so. The CEF log shows the process received a "bad IPC message, reason 213" and terminated a renderer tab shortly before the SIGBUS — it was under load, processing web content.
What the evidence shows
This is not an isolated crash. The coredump list reveals a clear pattern:
Date Time Signal
Aug 15 23:07–23:18 SIGBUS ×7
Aug 15 23:15:11 SIGBUS
Aug 16 23:10–23:27 SIGBUS ×10
Aug 16 23:39:30 SIGBUS
Aug 17 23:33–23:41 SIGBUS ×8
Aug 17 23:58:23 SIGBUS
Hyprland itself crashes with SIGBUS in the same bursts. Its backtrace (coredumpctl info 63284) is:
#0 libc SIGBUS
#1 CDMABUFFormatTable::CDMABUFFormatTable() (Hyprland)
#2 CLinuxDMABufV1Protocol::resetFormatTable()
#3 CMonitor::onDisconnect()
#4 SDRMConnector::disconnect()
#5 CDRMBackend::recheckOutputs()
#6 CSession::dispatchUdevEvents()
This is a GPU/display subsystem failure. The sequence is: udev detects a display change → DRM rechecks outputs → connector disconnects → Hyprland tries to rebuild its DMA-BUF format table → SIGBUS when mapping GPU memory.
Contributing factors found
1. USB device resets: A wireless keyboard (Kanata WG9, device usb 1-1.6) resets every ~32 seconds for extended periods, correlated with the crash bursts. This suggests broader USB/system bus instability.
2. Display hot-plug cycling: The journal shows repeated "FALLBACK" monitor removal/re-add events in the seconds before each crash cluster, indicating the display connection is flapping.
3. amdgpu driver warning: amdgpu 0000:03:00.0: [drm] Unknown EDID CEA parser results appears during crash windows.
4. Failing sdb disk: The WDC WD5003ABYX (500GB, /dev/sdb) shows uncorrectable I/O errors (UNC) at boot. It is not mounted and not directly implicated in this crash, but it indicates a broader hardware concern.
5. Memory is fine: 31Gi total, 26Gi free, no swap usage, no OOM kills.
Most likely cause
GPU driver or hardware instability on the AMD RX 6600 (Navi 23). The display connection is intermittently dropping, and when Hyprland or Steam's CEF tries to access the GPU-backed memory-mapped regions during the disconnect/reconnect, the kernel delivers SIGBUS because those pages are no longer valid.
This is a convergence of:
- The amdgpu driver struggling with display connector events (possibly related to the Samsung S24R350 HDMI connection)
- Hyprland crashing in its own DMA-BUF code during monitor disconnect handling (a Hyprland bug in error recovery, or the driver is delivering an unrecoverable state)
- Steam/CEF hitting the same GPU memory mapping failure as a downstream consequence
What to do
This is not an Omarchy configuration bug — it's a Hyprland/driver/hardware issue. Suggested actions:
1. Check your HDMI cable and port — the display flapping pattern suggests a physical connection issue
2. Try a different HDMI port on the RX 6600 if available
3. Update GPU firmware: sudo pacman -S linux-firmware-amdgpu (you have 20260810, check if newer exists)
4. Consider disabling the failing sdb drive in BIOS if not in use — the I/O errors could indicate broader PSU or SATA bus issues
5. Report the Hyprland DMA-BUF crash at https://github.com/hyprwm/Hyprland/issues — the CDMABUFFormatTable constructor should handle SIGBUS gracefully rather than dying
Data loss
No user data was lost. Steam automatically restarts steamwebhelper after each crash. The Dota 2 crashes in the log are separate SIGSEGV events (likely in-game, not related to this display issue).
Recurrence
Likely to recur until the underlying GPU/display instability is addressed. The pattern has repeated across 3 consecutive days at similar evening hours (23:00–24:00 WIB), suggesting it may be triggered by specific usage patterns (gaming sessions, display power management, or thermal conditions).

above are report that ai told me after crash

View raw text
### System details

amd rx6600, ryzen 5600g, omarchy v4

### What's wrong?

Crash Report: steamwebhelper PID 4073892
What crashed and what it was doing
steamwebhelper (Valve's embedded Chromium browser for Steam) died with SIGBUS (BUS_ADRERR) while running a memory copy in V_memcpy_nocache inside Valve's libvstdlib_s.so. The CEF log shows the process received a "bad IPC message, reason 213" and terminated a renderer tab shortly before the SIGBUS — it was under load, processing web content.
What the evidence shows
This is not an isolated crash. The coredump list reveals a clear pattern:
Date	Time	Signal
Aug 15	23:07–23:18	SIGBUS ×7
Aug 15	23:15:11	SIGBUS
Aug 16	23:10–23:27	SIGBUS ×10
Aug 16	23:39:30	SIGBUS
Aug 17	23:33–23:41	SIGBUS ×8
Aug 17	23:58:23	SIGBUS
Hyprland itself crashes with SIGBUS in the same bursts. Its backtrace (coredumpctl info 63284) is:
#0  libc SIGBUS
#1  CDMABUFFormatTable::CDMABUFFormatTable()  (Hyprland)
#2  CLinuxDMABufV1Protocol::resetFormatTable()
#3  CMonitor::onDisconnect()
#4  SDRMConnector::disconnect()
#5  CDRMBackend::recheckOutputs()
#6  CSession::dispatchUdevEvents()
This is a GPU/display subsystem failure. The sequence is: udev detects a display change → DRM rechecks outputs → connector disconnects → Hyprland tries to rebuild its DMA-BUF format table → SIGBUS when mapping GPU memory.
Contributing factors found
1. USB device resets: A wireless keyboard (Kanata WG9, device usb 1-1.6) resets every ~32 seconds for extended periods, correlated with the crash bursts. This suggests broader USB/system bus instability.
2. Display hot-plug cycling: The journal shows repeated "FALLBACK" monitor removal/re-add events in the seconds before each crash cluster, indicating the display connection is flapping.
3. amdgpu driver warning: amdgpu 0000:03:00.0: [drm] Unknown EDID CEA parser results appears during crash windows.
4. Failing sdb disk: The WDC WD5003ABYX (500GB, /dev/sdb) shows uncorrectable I/O errors (UNC) at boot. It is not mounted and not directly implicated in this crash, but it indicates a broader hardware concern.
5. Memory is fine: 31Gi total, 26Gi free, no swap usage, no OOM kills.
Most likely cause
GPU driver or hardware instability on the AMD RX 6600 (Navi 23). The display connection is intermittently dropping, and when Hyprland or Steam's CEF tries to access the GPU-backed memory-mapped regions during the disconnect/reconnect, the kernel delivers SIGBUS because those pages are no longer valid.
This is a convergence of:
- The amdgpu driver struggling with display connector events (possibly related to the Samsung S24R350 HDMI connection)
- Hyprland crashing in its own DMA-BUF code during monitor disconnect handling (a Hyprland bug in error recovery, or the driver is delivering an unrecoverable state)
- Steam/CEF hitting the same GPU memory mapping failure as a downstream consequence
What to do
This is not an Omarchy configuration bug — it's a Hyprland/driver/hardware issue. Suggested actions:
1. Check your HDMI cable and port — the display flapping pattern suggests a physical connection issue
2. Try a different HDMI port on the RX 6600 if available
3. Update GPU firmware: sudo pacman -S linux-firmware-amdgpu (you have 20260810, check if newer exists)
4. Consider disabling the failing sdb drive in BIOS if not in use — the I/O errors could indicate broader PSU or SATA bus issues
5. Report the Hyprland DMA-BUF crash at https://github.com/hyprwm/Hyprland/issues — the CDMABUFFormatTable constructor should handle SIGBUS gracefully rather than dying
Data loss
No user data was lost. Steam automatically restarts steamwebhelper after each crash. The Dota 2 crashes in the log are separate SIGSEGV events (likely in-game, not related to this display issue).
Recurrence
Likely to recur until the underlying GPU/display instability is addressed. The pattern has repeated across 3 consecutive days at similar evening hours (23:00–24:00 WIB), suggesting it may be triggered by specific usage patterns (gaming sessions, display power management, or thermal conditions).

above are report that ai told me after crash

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.