Hello, yesterday sep. 22, 2025 I was able to launch normally.
And later on (around 10pm CEST) the bug appeared : executing the launcher does apparently nothing.
Launching from the terminal gives this output :
./launcher
X Error of failed request: BadRROutput (invalid Output parameter)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 9 (RRGetOutputInfo)
Serial number of failed request: 15
Current serial number in output stream: 15
I tried on another fresh install of Linux Mint and it does the same.
Same also with the latest launcher downloaded from WT web site.
non of my linux laptops (one monitor) run into this, could try removing a couple or download files through a laptop
the old launcher runs once, self updates, but keeps running, meaning if have an old tar you can copy the launcher and launcherr.dat over into your main dir and run it like that once, it’ll update everything, you can run it directly through linux64/aces later
I suspect they did something funky with display detection, possibly related to xwayland which carried over to horrible workings on x11
Same issue here. I couldn’t find anywhere an older version of the launcher, but luckily, WT makes a backup of the old launcher before updating to the latest version. To be able to play, I did this:
Go to the War thunder installation folder, enter the /update/bak/ folder
Copy the files from this folder (these should be the Launcher files ) to the main installation directory e.g. WarThunder/
When asked if it’s ok to overwrite, select yes for all files
Run the Launcher as usual, it should start and download the Tusk Force update.
The operation might need to be repeated until Gaijin fixes the launcher.
From what I can see so far this only seems to be affected users on slightly older versions of Xorg/X11 so could all of you that are experiencing this please confirm your Xorg/X11 version by posting the output of the inxi -F command?
Also could everyone that hasn’t already please submit a bug report for this issue as well so the cause can be narrowed down?
the laptops also run x11, with the same versions of x11 as well all my installs are roughly the same day of updates from arch. granted, they all lack the graphics to actually run the game, I merely had them on hand to mess around with the launcher
Graphics:
Device-1: ASPEED Graphics Family driver: ast v: kernel
Device-2: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
470/480/570/570X/580/580X/590] driver: amdgpu v: kernel
Device-3: Logitech StreamCam
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB
Display: unspecified server: X.Org v: 21.1.18 driver: X:
loaded: amdgpu,modesetting dri: radeonsi gpu: amdgpu,ast resolution:
1: 1920x1080~60Hz 2: 1920x1080~60Hz 3: 1920x1080~60Hz 4: N/A
API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.2.1-arch1.2
renderer: AMD Radeon RX 570 Series (radeonsi polaris10 ACO DRM 3.64
6.16.3-arch1-1)
API: Vulkan v: 1.4.321 drivers: radv surfaces: N/A
Hello! I had the same problem. Launcher started the day before, but not the next day! Deleting Warthunder (Linux Mint) and downloading the latest launcher (wt_launcher_linux_1.0.3.31) does not solve the problem. The WT launcher won’t start! I found an older version (wt_launcher_linux_0.9.4.92) on my hard drive. The WT launcher starts with this version. Now I’m downloading the game…
You should find an older version of the launcher in your game directory, in /update/bak
Backup the launcher and launcherr.dat files that are in this sub-directory.
Then put them in the game directory (replace the newest ones) and try.
If it works the game will be updated.
Then you can execute the game from /linux64/aces
You may have to do this copy every time you want to update the game, because the launcher will update itself automatically.
heres the 1.0.3.26 I 've been using, any older one besides really close to it seems to be fine wt_launcherfiles_1_0_3_26.zip — Yandex Disk (just copy launcher and launcherr.dat over)
I’ve also tried with a single display setup on the main system today and couldnt get it to work that way either, remains a mystery why but I assume you guys changed something in the launcher where it makes the XRRGetOutputInfo call.
from what I see online this might happen with empty display parameter in the call, you guys checking anything differently?
