Skip to content
PassTheTorch

Playing on Linux

Blizzard does not support Linux and Valve has closed the Proton ticket for Forever as “not planned”, but the beta runs fine once you know the three or four settings that matter. Guild members on Linux hit the same wall in the same order: a launcher that will not log in, a loading screen that freezes, an Error 109 thread freeze, and single-digit FPS from a debug variable. Every fix on this page was confirmed by players on the Blizzard forums or by a guild member on the beta client, and the page stays generic so it works for any distro.

Official position

Section titled “Official position”

Blizzard moderators state that Linux is unsupported. Valve closed Proton issue #10156 as “unofficial game, not planned”. Steam Deck results are mixed. verified None of that stops it from working; it means nobody will fix a regression for you, so keep notes on what you changed.

Section titled “Route 1: Lutris (recommended)”

This is the route a guild member used for the beta, verified working on 2026-09-22 with Battle.net installed, logged in, and the Forever beta downloading at full speed. verified

  1. Install Lutris as a user flatpak. flatpak install --user flathub net.lutris.Lutris. No sudo needed if Flathub is a user remote.
  2. Install the umu launcher. The Flathub Lutris build does not bundle umu, so any Proton runner (its default is proton-cachyos) fails with “Install umu to use Proton”. Fix: download the umu-launcher-<version>-zipapp.tar from the Open-Wine-Components/umu-launcher GitHub releases, extract it, and drop umu-run at ~/.var/app/net.lutris.Lutris/data/lutris/runtime/umu/umu-run, then chmod +x it. That is a path Lutris searches. A Lutris flatpak update may not touch it; re-check after flatpak update. verified
  3. Install the runtime components. A fresh flatpak can have no runtime at all (“DXVK runtime component is not installed”). Open Preferences, then Updates, and let it fetch everything. verified
  4. Run the official Battle.net script from Lutris (search “Battle.net”, the standard install). Do not log in during the first installer run; let it finish, then launch. verified
  5. Log in, install World of Warcraft, and pick the Forever branch. During the beta it is the _classic_beta_ folder (WowB.exe). The prefix defaults to ~/Games/battlenet, and WoW lands at <prefix>/drive_c/Program Files (x86)/World of Warcraft/.
  6. Launch from Lutris. Play on Battle.net, then Play on WoW.

Why Lutris over the Steam route: Battle.net’s launcher has Wine quirks (a blank CEF login page, a stuck updater) that the Lutris script already handles. The Steam route works too, but expects manual shortcut fixes after install.

Route 2: Battle.net as a non-Steam game

Section titled “Route 2: Battle.net as a non-Steam game”

Add Battle.net’s installer to Steam as a non-Steam game, force GE-Proton or Proton 10+ in compatibility, run the installer, then swap the shortcut target to the installed Battle.net.exe. The two maintained guides:

  • GamingOnLinux, updated May 2026, covers desktop, SteamOS and Steam Deck. verified
  • sudowheel’s Battle.net on Linux guide. verified

Known install gotchas from those guides: do not log in during the first run; Flatpak Lutris has a 32-bit Wine issue (the umu route above sidesteps it); the BLZBNTBNA00000005 agent error is fixed by deleting the Agent data directory and relaunching. verified

One fan site gives a Steam launch option of --game=wow_classic_beta --install for the beta. unverified

The in-game fixes (confirmed on the Forever beta)

Section titled “The in-game fixes (confirmed on the Forever beta)”

All three come from Blizzard forum threads where Linux players compared notes, as of 2026-09-19. verified

Symptom Fix Where
Freeze on the loading screen Launch with -dx11 (or set Graphics API to DirectX 11 in System settings). If you insist on DX12, drop graphics one notch below max. Launch args or System, Advanced
ERROR #109 thread freeze, 3-minute loads, severe FPS hitching Set Secondary Lighting to Fair. System, Graphics
Single-digit FPS Remove PROTON_LOG=1 from your environment or launch options. It was left over from debugging and tanks performance. Steam launch options or Lutris environment
Stutter under DX12 Switch to DX11 in game. System settings

Launcher gotchas

Section titled “Launcher gotchas”
Symptom Fix
Blank Battle.net login page Disable hardware acceleration in Battle.net settings.
Battle.net window vanishes when WoW starts Normal launcher behavior, not a Wine bug. Battle.net Settings, General, “When I launch a game”. Edit while Battle.net is not running or it overwrites your choice on exit.
Stuck updater or agent error BLZBNTBNA00000005 Delete the Agent data directory and relaunch.
Games broke after an NVIDIA driver upgrade Flatpak Lutris pulls the NVIDIA GL runtime matching your host driver. Run flatpak update --user before blaming Wine.
Log line about vulkaninfo missing Harmless.
Disk WoW Classic-family installs are around 50 GB. Check space before you start.

Addon managers on Linux

Section titled “Addon managers on Linux”

The Forever client reads <prefix>/drive_c/Program Files (x86)/World of Warcraft/<flavor>/Interface/AddOns/, where <flavor> is _classic_beta_ during the beta and something not yet confirmed at launch (see Addons). Two native options:

  • WowUp-CF AppImage. Version 2.23.1 (Sep 1, 2026) ships a native Linux build; the 2.24.0 beta adds “More WoW Forever integrations”. Download the AppImage, chmod +x, run it, and add the WoW folder inside your prefix as a client. verified
  • instawow. CLI and GUI, pulls from CurseForge, Wago, GitHub and Tukui. Point it at the same AddOns folder. Forever is not mentioned in its docs, so pick the flavor by hand if it asks. verified

The CurseForge app has a Linux build according to search results, but its download page loaded empty and whether it lists Forever as a flavor is unconfirmed. partially verified

Rules do not change on Linux: only CurseForge, Wago or GitHub, only Forever-flagged projects, never a “Forever addon pack” installer.

Unknown as of 2026-09-24

Section titled “Unknown as of 2026-09-24”
  • The live addon folder name after November 4.
  • Whether the --game=wow_classic_beta --install Steam flag is correct (single fan-site source).
  • Whether the CurseForge app on Linux lists Forever.
  • Steam Deck performance at launch (beta results mixed).
  • Whether the ERROR #109 and loading-screen fixes are still needed after the launch client build.

Sources

Section titled “Sources”