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

Hyprland crash after DP-1 hotplug on NVIDIA session

Reported by lbybrilee · filed May 5, 2026 · 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

Hyprland crash after DP-1 hotplug on NVIDIA sessionrevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Omarchy 3.7.0
Arch Linux, kernel 7.0.3-arch1-2
GPU: NVIDIA RTX 4070 Ti SUPER, nvidia-open-dkms 595.71.05-2
Monitor: Samsung LC34G55T on DP-1, [email protected]
Session: Hyprland under uwsm

Relevant packages:

hyprland 0.54.3-4
aquamarine 0.11.0-2
hyprutils 0.13.0-1
hyprgraphics 0.5.1-2
nvidia-open-dkms 595.71.05-2
nvidia-utils 595.71.05-2
libinput 1.31.1-1
pixman 0.46.4-1
xdg-desktop-portal-hyprland 1.3.12-2
uwsm 0.26.4-1

What's wrong?

Hyprland crashed at 2026-05-06 06:21:11 KST after my only monitor briefly dropped off DP-1 and came back. I do not know yet whether the bug is in Omarchy, Hyprland, Aquamarine, or NVIDIA, but it happened inside the Omarchy Hyprland session and uwsm had to restart it.

The crash report was written to:

~/.cache/hyprland/hyprlandCrashReport1217.txt

The crash report starts with:

Hyprland received signal 11(SEGV)
Version: 521ece463c4a9d3d128670688a34756805a4328f
Tag: v0.54.3

The stack points at monitor damage while Hyprland was handling a mouse button event:

CMonitor::isMirror()
CHyprRenderer::damageMonitor(...)
CCompositor::changeWindowZOrder(...)
CInputManager::processMouseDownNormal(...)
CInputManager::onMouseButton(...)
Aquamarine::CSession::handleLibinputEvent(...)

Right before the crash, the previous Hyprland log shows DP-1 being disabled, reported disconnected, then connected again:

drm: Disabling output DP-1
drm: Modesetting DP-1 with [email protected]
[libinput] client bug: timer button-debounce-debounce-event3: scheduled expiry is in the past (-34ms), your system is too slow
drm: Got a hotplug event for /dev/dri/card1
drm: Connector DP-1 disconnected
drm: Disabling output DP-1
drm: Connector DP-1 is not connected, removing old crtc 62
drm: Got a hotplug event for /dev/dri/card1
drm: Connector DP-1 connected
drm: Connecting connector DP-1, CRTC ID 62

After Hyprland died, xdg-desktop-portal-hyprland also segfaulted in libwayland-client. That looks secondary because the compositor was already gone:

xdg-desktop-portal-hyprland.service: Main process exited, code=dumped, status=11/SEGV

uwsm restarted Hyprland. The new session came back, but a few seconds later it logged repeated pixman errors:

In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on _pixman_log_error to debug

There is also a config warning on restart:

source= globbing error: found no match

That seems to come from this line when the toggles directory is empty:

source = ~/.local/state/omarchy/toggles/hypr/*.conf

I tried to run omarchy-debug, but from this noninteractive shell it could not prompt for sudo and did not produce a report. I can attach the full Hyprland crash report and the relevant hyprland.log tail if useful.

View raw text
System details

```text
Omarchy 3.7.0
Arch Linux, kernel 7.0.3-arch1-2
GPU: NVIDIA RTX 4070 Ti SUPER, nvidia-open-dkms 595.71.05-2
Monitor: Samsung LC34G55T on DP-1, [email protected]
Session: Hyprland under uwsm
```

Relevant packages:

```text
hyprland 0.54.3-4
aquamarine 0.11.0-2
hyprutils 0.13.0-1
hyprgraphics 0.5.1-2
nvidia-open-dkms 595.71.05-2
nvidia-utils 595.71.05-2
libinput 1.31.1-1
pixman 0.46.4-1
xdg-desktop-portal-hyprland 1.3.12-2
uwsm 0.26.4-1
```

What's wrong?

Hyprland crashed at `2026-05-06 06:21:11 KST` after my only monitor briefly dropped off DP-1 and came back. I do not know yet whether the bug is in Omarchy, Hyprland, Aquamarine, or NVIDIA, but it happened inside the Omarchy Hyprland session and uwsm had to restart it.

The crash report was written to:

```text
~/.cache/hyprland/hyprlandCrashReport1217.txt
```

The crash report starts with:

```text
Hyprland received signal 11(SEGV)
Version: 521ece463c4a9d3d128670688a34756805a4328f
Tag: v0.54.3
```

The stack points at monitor damage while Hyprland was handling a mouse button event:

```text
CMonitor::isMirror()
CHyprRenderer::damageMonitor(...)
CCompositor::changeWindowZOrder(...)
CInputManager::processMouseDownNormal(...)
CInputManager::onMouseButton(...)
Aquamarine::CSession::handleLibinputEvent(...)
```

Right before the crash, the previous Hyprland log shows DP-1 being disabled, reported disconnected, then connected again:

```text
drm: Disabling output DP-1
drm: Modesetting DP-1 with [email protected]
[libinput] client bug: timer button-debounce-debounce-event3: scheduled expiry is in the past (-34ms), your system is too slow
drm: Got a hotplug event for /dev/dri/card1
drm: Connector DP-1 disconnected
drm: Disabling output DP-1
drm: Connector DP-1 is not connected, removing old crtc 62
drm: Got a hotplug event for /dev/dri/card1
drm: Connector DP-1 connected
drm: Connecting connector DP-1, CRTC ID 62
```

After Hyprland died, `xdg-desktop-portal-hyprland` also segfaulted in `libwayland-client`. That looks secondary because the compositor was already gone:

```text
xdg-desktop-portal-hyprland.service: Main process exited, code=dumped, status=11/SEGV
```

uwsm restarted Hyprland. The new session came back, but a few seconds later it logged repeated pixman errors:

```text
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on _pixman_log_error to debug
```

There is also a config warning on restart:

```text
source= globbing error: found no match
```

That seems to come from this line when the toggles directory is empty:

```text
source = ~/.local/state/omarchy/toggles/hypr/*.conf
```

I tried to run `omarchy-debug`, but from this noninteractive shell it could not prompt for sudo and did not produce a report. I can attach the full Hyprland crash report and the relevant `hyprland.log` tail if useful.

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 02:53 UTC