Identify the failing layer
Lutris manages installers and runners but is not itself the Wine loader or the game's Vulkan implementation. A blank game window after clicking Play can arise from runner selection, an incomplete installer, an external launcher, missing 32-bit graphics support or a hardware problem. Identify the selected runner and the exact installed game path before changing versions. A system wine --version output does not necessarily describe the Wine build actually selected inside Lutris.
Collect discriminating evidence
The project documents launching Lutris with lutris -d for installer debugging and enabling game-specific runner debug output before reproducing a failure. Collect the last game's log, note the selected prefix, and separate installer output from execution output. Lines marked fixme by Wine often indicate unimplemented behavior without proving a crash. Correlate actual err lines and exit behavior with nearby kernel messages only if there was also a system-level stall.
Compare safely and record limitations
Test one change at a time, such as reverting the runner selection or temporarily disabling one injected overlay. For games using a modern Proton runner outside Steam, verify the external-client runtime path including umu instead of copying Steam launch flags blindly. Reinstalling the whole game or prefix erases useful before-and-after evidence and risks saves; it is not a first diagnostic step. Be explicit when Battle.net, Ubisoft Connect or EA App adds its own failure boundary.
Gather evidence before changing the system
Run one command at a time in the relevant host or game environment. Read its requirements and interpretation first. The website displays commands and never runs them.
Temporary diagnostic environment
lutris -dRequirements: Run in the relevant host/session; compare with the actual game environment and redact private paths before sharing.
Launch Lutris with debug output in a terminal; inspect credentials before sharing.
Read-only observation
vulkaninfo --summaryRequirements: Run in the relevant host/session; compare with the actual game environment and redact private paths before sharing.
Only describes host-side Vulkan unless run in the same environment as the game.
A controlled test with a way back
Save the runner and prefix path, capture the last game log, and compare one compatible runner without deleting any user data.
Rollback: Restore the previous runner and per-game environment overrides.
What this test cannot establish: Lutris and launchers change frequently; no runner choice guarantees title-specific support.
Sources and scope
This editorial review uses primary project and distribution references. It does not establish that a fix has been reproduced on your hardware. Installed versions, the game runtime and the selected graphics API can change the result.
- Lutris official logging instructions
Lutris describes launcher debug mode and the last-game log.
- umu-launcher documented workflow
umu supplies an external-client Proton runtime rather than implying Steam compatibility.