• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

BaumiBaumann

Recruit
46 Badges
Nov 25, 2024
4
0
  • Stellaris: Lithoids
  • Cities: Skylines - Green Cities
  • Hearts of Iron IV: Expansion Pass
  • Stellaris: Humanoids Species Pack
  • Stellaris: Apocalypse
  • Cities: Skylines - Parklife
  • Stellaris: Distant Stars
  • Cities: Skylines Industries
  • Stellaris: Megacorp
  • Hearts of Iron IV: Expansion Pass
  • Cities: Skylines - Campus
  • Stellaris: Ancient Relics
  • Stellaris: Synthetic Dawn
  • Hearts of Iron IV: La Resistance
  • Stellaris: Federations
  • Crusader Kings III
  • Crusader Kings III: Royal Edition
  • Battle for Bosporus
  • Stellaris: Necroids
  • Stellaris: Nemesis
  • Hearts of Iron IV: By Blood Alone
  • Hearts of Iron IV: No Step Back
  • Hearts of Iron 4: Arms Against Tyranny
  • Stellaris: Galaxy Edition
  • Europa Universalis IV
  • Europa Universalis IV: Conquest of Paradise
  • Europa Universalis IV: Wealth of Nations
  • Europa Universalis IV: Call to arms event
  • Europa Universalis IV: Res Publica
  • Cities: Skylines
  • Cities: Skylines Deluxe Edition
  • Cities: Skylines - After Dark
  • Cities: Skylines - Snowfall
  • Stellaris
  • Stellaris: Galaxy Edition
  • Crusader Kings II
  • Stellaris: Galaxy Edition
  • Hearts of Iron IV: Cadet
  • Stellaris: Digital Anniversary Edition
  • Stellaris: Leviathans Story Pack
  • Cities: Skylines - Natural Disasters
  • Hearts of Iron IV: Together for Victory
  • Stellaris - Path to Destruction bundle
  • Cities: Skylines - Mass Transit
  • Surviving Mars
  • Hearts of Iron IV: Death or Dishonor

Integrity​

I have verified my game files (on Steam)​

Yes

I have disabled all mods​

Yes

Required​

Summary​

Linux version doesnt start

Description​

As someone has already pointed out on ProtonDB, the game crashes on startup. However, if you bypass the launcher and start the victoria3 binary directly, the game launches correctly, indicating that the issue is likely with the launcher.

I have only tested this on Wayland.
I also tried deleting all Paradox Launcher folders from my system and reinstalling the game, but it had no effect.
By the way, this issue only started after the 1.8 update. The Paradox Launcher still works for the Hearts of Iron IV Linux version, even after the latest DLC.

Steps to reproduce​

Start the game

Game Version​

1.8.3

OS​

Linux (Other)

Additional​

Bug Type​

Crash to Desktop

Save Game​



Attachments​



Player Pain​

8

 
Last edited:
Hi! Are there any logs in $HOME/.local/share/Paradox Interactive/Victoria 3/crashes (or your distro equivalent of this path?).
For the launcher logs, they should be within ~/.local/share/Paradox Interactive/launcher-v2

We only officially support Ubuntu 22.04 and the game runs natively on it (without the need for Proton), but we can send the logs to our launcher team for further investigation.
 
Hi! Are there any logs in $HOME/.local/share/Paradox Interactive/Victoria 3/crashes (or your distro equivalent of this path?).
For the launcher logs, they should be within ~/.local/share/Paradox Interactive/launcher-v2

We only officially support Ubuntu 22.04 and the game runs natively on it (without the need for Proton), but we can send the logs to our launcher team for further investigation.
Hi, thanks for the quick response. On a clean install, the game doesn't launch because the launcher fails to start, meaning the $HOME/.local/share/Paradox Interactive/Victoria 3/ directory doesn’t exist initially.

Regarding the logs in ~/.local/share/Paradox Interactive/launcher-v2, the main log file is empty, and the others don't seem particularly relevant.

I’ve recorded a screen capture of the entire process. Please ignore the fact that I force quit the game at the end—it would have started and worked if I had waited a bit longer. Let me know if I can assist in any other way.

 

Attachments

  • launcher-installer.log
    667,7 KB · Views: 0
  • launcher-dowser.log
    407 bytes · Views: 0
  • launcher-bootstrapper.log
    2 KB · Views: 0
Judging from the repeated "DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau." errors, I can only assume it's a driver setup issue - The game is only supported on standard Ubuntu configs with (for Nvidia GPUs) proprietary Nvidia drivers. I'm afraid the QA can't help more with such specific setups, so I'll move the thread to our Technical Support in case they have any more troubleshooting tips.
 
Judging from the repeated "DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau." errors, I can only assume it's a driver setup issue - The game is only supported on standard Ubuntu configs with (for Nvidia GPUs) proprietary Nvidia drivers. I'm afraid the QA can't help more with such specific setups, so I'll move the thread to our Technical Support in case they have any more troubleshooting tips.
I just wanted to provide an update on how I fixed this. I had the following environment variable set:

ELECTRON_OZONE_PLATFORM_HINT=auto

For some reason, this causes the Victoria 3 launcher to crash, whereas the Hearts of Iron IV launcher is unaffected. This environment variable is typically used to instruct Chromium-based applications to use Wayland instead of X11. I personally use it to force Discord and Visual Studio Code to run in Wayland mode.

It seems that, unlike the Hearts of Iron IV launcher, the Victoria 3 launcher responds to this variable and attempts to run as a Wayland window, which then fails.

Regarding your repeated notes about only supporting Ubuntu, this issue will also affect Ubuntu users.
 
I just wanted to provide an update on how I fixed this. I had the following environment variable set:

ELECTRON_OZONE_PLATFORM_HINT=auto

For some reason, this causes the Victoria 3 launcher to crash, whereas the Hearts of Iron IV launcher is unaffected. This environment variable is typically used to instruct Chromium-based applications to use Wayland instead of X11. I personally use it to force Discord and Visual Studio Code to run in Wayland mode.

It seems that, unlike the Hearts of Iron IV launcher, the Victoria 3 launcher responds to this variable and attempts to run as a Wayland window, which then fails.

Regarding your repeated notes about only supporting Ubuntu, this issue will also affect Ubuntu users.
Just to be clear, by "fixed this" I mean resolving the issue with the game not starting, not the "DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau." errors. Those messages are unrelated to your game and can be safely ignored.
 
I had the following environment variable set:

ELECTRON_OZONE_PLATFORM_HINT=auto

For some reason, this causes the Victoria 3 launcher to crash, whereas the Hearts of Iron IV launcher is unaffected.
Those two games use the same installation of the same launcher, so it is hard to understand why one is affected but not the other!