# Proposed GitHub issue

Repository: `basecamp/omarchy`

## Title

Quickshell SIGSEGV in Mesa `dri2_query_image` when Omarchy keyboard panel opens

## Body

### System details

- Omarchy at crash time: 4.0.0 (`omarchy version` now reports 4.0.1-1)
- Quickshell: 0.3.0, revision `28771c7c74b42e20afca0b1b63980cb46515537c` (`quickshell-git`)
- Qt: 6.11.2
- Mesa Gallium: 26.1.8-arch1.1
- GPUs: Intel Iris Xe (`i915`, PCI 00:02.0) and NVIDIA RTX 4070 (`nvidia-drm`, PCI 01:00.0)
- Shell config: `/usr/share/omarchy/shell/shell.qml`

The installed Omarchy 4.0.1 CLI does not provide the previously documented `omarchy debug --no-sudo --print` command, so the relevant system and crash details are included directly below.

### What happened

Quickshell crashed twice with SIGSEGV while the shipped Omarchy keyboard panel was opening. Quickshell restarted automatically after each crash; no user-data loss was observed.

The two crashes occurred at 01:42:32 and 01:44:34 EDT on 2026-08-25. Immediately before both crashes, the Quickshell log recorded:

```text
Received event: "openlayer>>omarchy-keyboard-panel-dismiss"
Received event: "openlayer>>omarchy-keyboard-panel"
```

### Expected behavior

Opening the keyboard-focused Omarchy panel should display the panel without terminating and restarting Quickshell.

### Reproduction

1. Run the standard Omarchy Quickshell from `/usr/share/omarchy/shell/shell.qml`.
2. Open an Omarchy bar panel that uses the shared keyboard-panel layer.
3. Quickshell may terminate with SIGSEGV and then restart automatically.

This reproduced twice in succession on this machine. The evidence identifies panel opening as the repeatable trigger, but does not establish that every invocation crashes.

### Backtrace

Both cores have the same relevant rendering stack on `QSGRenderThread`:

```text
#0  libc.so.6
#1  dri2_query_image at /usr/lib/libgallium-26.1.8-arch1.1.so
#2  libEGL_mesa.so.0
#3  libEGL_mesa.so.0
#4  libEGL_mesa.so.0
#5  QtWaylandClient::QWaylandGLContext::swapBuffers(QPlatformSurface*)
#6  libQt6Gui.so.6
#7  QRhi::endFrame(QRhiSwapChain*, QFlags<QRhi::EndFrameFlag>)
#8  libQt6Quick.so.6
#9  libQt6Core.so.6
#10 libc.so.6
#11 libc.so.6
```

### Evidence limits

The cores prove that the immediate fault occurs in Mesa's EGL/Gallium path while Qt Wayland swaps a buffer, and the two logs independently identify opening `omarchy-keyboard-panel` as the preceding trigger. They do not prove whether ownership is in Omarchy's surface lifecycle, Qt Wayland, or Mesa, nor which GPU handled the affected surface.

Memory pressure and an observed GPU reset were ruled out: the machine had about 51 GiB of 62 GiB RAM available, swap was unused, and there were no contemporaneous OOM, GPU-reset, ring-timeout, or NVIDIA XID messages.

The local Quickshell reports are retained at:

```text
~/.cache/quickshell/crashes/ft07539bkt/report.txt
~/.cache/quickshell/crashes/ft07w69bkt/report.txt
```

Filed by GPT-5 via Codex.