A report is only useful if someone else can tell whether it applies to them. These are the details that make that possible, and the commands that produce them.
Distro and kernel
cat /etc/os-release | head -2
uname -r
The kernel matters more than people expect — GPU drivers, anti-cheat and controller support all move with it.
GPU and driver
Mesa (AMD and Intel):
glxinfo -B | grep -E "Device|OpenGL version"
vulkaninfo --summary | grep -E "driverName|driverInfo"
NVIDIA:
nvidia-smi --query-gpu=name,driver_version --format=csv,noheader
If glxinfo or vulkaninfo is missing, they live in mesa-utils and vulkan-tools on most distros.
Proton or Wine build
Say exactly which one, because the differences between them are the whole point:
- Proton — Valve's, shipped through Steam. Versioned like
10.0-3.
- Proton Experimental — a rolling build, changes daily.
- Proton-GE — a community build with extra media codecs and patches, versioned like
GE-Proton11-7.
- Wine — upstream, used directly by Lutris, Bottles and Heroic.
wine --version.
Launch options
Paste the exact string. PROTON_USE_WINED3D=1 %command% and %command% -dx11 are different reports.
What happened
Where it broke matters more than that it broke. "Crashes on launch" and "crashes when entering a dungeon" point at completely different causes.
The date
Put it in. A driver release or a game patch can invalidate a report overnight, and an undated "works fine" tells a reader nothing about whether it still holds.
With the BlizzNux Launcher
The launcher gathers all of this for the reports it sends. To see it yourself, open Settings and press Run doctor: it shows the umu, Proton build, prefix and graphics offload in use.
