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

Battle.net installed via 'omarchy install gaming battlenet' silently exits before showing a window

Reported by pascalBokBok · filed Sep 18, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 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

Battle.net installed via 'omarchy install gaming battlenet' silently exits before showing a windowrevision 1 · captured 2026-09-28 21:23 UTC via poll

Environment

  • Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy
  • Intel Broadwell-U GT2 (HD Graphics 5500) iGPU only, no discrete GPU
  • GE-Proton11-6 and GE-Proton11-7, steamrt4 4.0.20260914, umu-launcher 1.4.4
  • /usr/share/vulkan/icd.d contains intel_icd.json (ANV), intel_hasvk_icd.json, and nvidia_icd.json (nvidia kernel module not loaded, no NVIDIA GPU present)

Steps to reproduce

  1. omarchy install gaming battlenet (installs umu-launcher, lib32 vulkan-intel, downloads and runs the Battle.net installer via umu-run)
  2. omarchy-launch-battlenet (or launch Battle.net from the app menu)

Expected

The Battle.net login window appears.

Actual

Nothing appears; the process exits quietly. From the desktop entry (Terminal=false) there is no output at all, so this looks exactly like "it just doesn't work".

Evidence (proton log, ~/steam-battlenet.log)

With GE-Proton11-7 the launcher dies with a C++ exception before the client spawns:

297.304:01d8:01dc:trace:seh:dispatch_exception code=e06d7363 (EXCEPTION_WINE_CXX_EXCEPTION) ...

With GE-Proton11-6 DXVK can't find any Vulkan device inside the umu container:

warn:  DXVK: No adapters found. Please check your device filter settings
warn:  and Vulkan drivers. A Vulkan 1.3 capable setup is required.
err:   Failed to initialize DXVK.
  • Host Vulkan is healthy (vkCreateInstance OK, 1 physical device enumerated).
  • This GPU is Gen 8 (Broadwell), which requires the intel_hasvk ICD; intel_icd.json (ANV) does not support Broadwell.
  • Pinning VK_ICD_FILENAMES to either ICD does not help — the container simply exposes no Vulkan device to DXVK.

Workaround that works

Running with PROTON_USE_WINED3D=1 makes Battle.net launch and render correctly (login window shows). The launcher script sets no such fallback.

Suggested fixes

  • omarchy-launch-battlenet should show an obvious error (and/or auto-fallback to PROTON_USE_WINED3D=1) when DXVK finds no adapter, instead of exiting silently.
  • Consider probing for a working Vulkan device inside the container up-front and falling back to the OpenGL path on hardware/installations where DXVK can't initialize.
View raw text
## Environment
- Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy
- Intel Broadwell-U GT2 (HD Graphics 5500) iGPU only, no discrete GPU
- GE-Proton11-6 and GE-Proton11-7, steamrt4 4.0.20260914, umu-launcher 1.4.4
- /usr/share/vulkan/icd.d contains `intel_icd.json` (ANV), `intel_hasvk_icd.json`, and `nvidia_icd.json` (nvidia kernel module not loaded, no NVIDIA GPU present)

## Steps to reproduce
1. `omarchy install gaming battlenet` (installs umu-launcher, lib32 vulkan-intel, downloads and runs the Battle.net installer via umu-run)
2. `omarchy-launch-battlenet` (or launch Battle.net from the app menu)

## Expected
The Battle.net login window appears.

## Actual
Nothing appears; the process exits quietly. From the desktop entry (`Terminal=false`) there is no output at all, so this looks exactly like "it just doesn't work".

## Evidence (proton log, `~/steam-battlenet.log`)
With GE-Proton11-7 the launcher dies with a C++ exception before the client spawns:
```
297.304:01d8:01dc:trace:seh:dispatch_exception code=e06d7363 (EXCEPTION_WINE_CXX_EXCEPTION) ...
```
With GE-Proton11-6 DXVK can't find any Vulkan device inside the umu container:
```
warn:  DXVK: No adapters found. Please check your device filter settings
warn:  and Vulkan drivers. A Vulkan 1.3 capable setup is required.
err:   Failed to initialize DXVK.
```
- Host Vulkan is healthy (`vkCreateInstance` OK, 1 physical device enumerated).
- This GPU is Gen 8 (Broadwell), which requires the `intel_hasvk` ICD; `intel_icd.json` (ANV) does not support Broadwell.
- Pinning `VK_ICD_FILENAMES` to either ICD does not help — the container simply exposes no Vulkan device to DXVK.

## Workaround that works
Running with `PROTON_USE_WINED3D=1` makes Battle.net launch and render correctly (login window shows). The launcher script sets no such fallback.

## Suggested fixes
- `omarchy-launch-battlenet` should show an obvious error (and/or auto-fallback to `PROTON_USE_WINED3D=1`) when DXVK finds no adapter, instead of exiting silently.
- Consider probing for a working Vulkan device inside the container up-front and falling back to the OpenGL path on hardware/installations where DXVK can't initialize.

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 15:44 UTC