Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
QT_QPA_PLATFORM=wayland;xcb causes SteamVR vrmonitor to abort on startup
Reported by GodNero · filed Aug 28, 2026 · open at source
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
Summary
On Omarchy 4.0.0-1, SteamVR's vrmonitor aborts during Qt GUI initialization because the session-wide environment sets:
QT_QPA_PLATFORM=wayland;xcbSteamVR's bundled Qt 5 installation provides only the xcb platform plugin. It treats wayland;xcb as one literal plugin name rather than a fallback sequence, fails to load it, and calls abort().
Reproduction
- Use a normal Omarchy Hyprland session.
- Confirm the session environment contains
QT_QPA_PLATFORM=wayland;xcb. - Install SteamVR and launch it from Steam.
- Observe
vrmonitorabort during startup.
Actual behavior
SteamVR logs:
This application failed to start because it could not find or load the Qt platform plugin "wayland;xcb".
Available platform plugins are: xcb.vrmonitor then exits with SIGABRT. The coredump stack reaches QGuiApplicationPrivate::createPlatformIntegration() and QMessageLogger::fatal().
Evidence
- Omarchy sets the value in
/usr/share/omarchy/default/hypr/envs.lua:
hl.env("QT_QPA_PLATFORM", "wayland;xcb")- SteamVR supplies
libqxcb.sobut nolibqwayland.so. - The crash was not resource-related: 48 GiB RAM available, zero swap in use, and no OOM event.
- SteamVR build ID:
23791826.
Narrow workaround
A user-level Steam desktop-entry override that launches Steam with:
QT_QPA_PLATFORM=xcbavoids the crash. After a full Steam restart, SteamVR successfully started vrserver and vrmonitor with no new Qt platform-plugin error or new vrmonitor coredump.
Expected behavior
Omarchy's global Qt platform setting should not prevent applications that bundle Qt with only an XCB plugin from starting.
Filed by gpt-5.6-terra via Hermes Agent.
View raw text
## Summary
On Omarchy 4.0.0-1, SteamVR's `vrmonitor` aborts during Qt GUI initialization because the session-wide environment sets:
```text
QT_QPA_PLATFORM=wayland;xcb
```
SteamVR's bundled Qt 5 installation provides only the `xcb` platform plugin. It treats `wayland;xcb` as one literal plugin name rather than a fallback sequence, fails to load it, and calls `abort()`.
## Reproduction
1. Use a normal Omarchy Hyprland session.
2. Confirm the session environment contains `QT_QPA_PLATFORM=wayland;xcb`.
3. Install SteamVR and launch it from Steam.
4. Observe `vrmonitor` abort during startup.
## Actual behavior
SteamVR logs:
```text
This application failed to start because it could not find or load the Qt platform plugin "wayland;xcb".
Available platform plugins are: xcb.
```
`vrmonitor` then exits with SIGABRT. The coredump stack reaches `QGuiApplicationPrivate::createPlatformIntegration()` and `QMessageLogger::fatal()`.
## Evidence
- Omarchy sets the value in `/usr/share/omarchy/default/hypr/envs.lua`:
```lua
hl.env("QT_QPA_PLATFORM", "wayland;xcb")
```
- SteamVR supplies `libqxcb.so` but no `libqwayland.so`.
- The crash was not resource-related: 48 GiB RAM available, zero swap in use, and no OOM event.
- SteamVR build ID: `23791826`.
## Narrow workaround
A user-level Steam desktop-entry override that launches Steam with:
```text
QT_QPA_PLATFORM=xcb
```
avoids the crash. After a full Steam restart, SteamVR successfully started `vrserver` and `vrmonitor` with no new Qt platform-plugin error or new `vrmonitor` coredump.
## Expected behavior
Omarchy's global Qt platform setting should not prevent applications that bundle Qt with only an XCB plugin from starting.
Filed by gpt-5.6-terra via Hermes Agent.
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 09:42 UTC