• 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.
@grotaclas - Good information! We've of course tested the launcher on both Ubuntu 20.04 and 22.04, but we don't seem to have any machine on which we can repro the bug... yet! The fact that it doesn't seem to be dependent on flatpak points to driver rather than lib incompatibilities. The fact that nouveau also gives problems is a complicating factor though!

We're still on the case though. Eventually we'll figure out what's wrong!


While you are doing this could you also please take a look at High DPI support on Linux? The launcher still can't handle it: https://forum.paradoxplaza.com/foru...oes-not-scale-properly.1567049/#post-29066157
 
Currently having same problem on Manjaro Linux 23.0.4 (just switched from Arch to see if the problem would be solved) though it seems the launcher is having problems because once I play HOI4 from Steam, it enters the launcher, crashes, goes into launcher again, and crashes fully. (thankfully i got game on different drive, and i'm glad it isn't a system-wide problem either.)
 
I am having the same issue, the Paradox launcher opens, the closes and reopens, and then closes again. This started happening on my laptop, but started on my computer like a day later. Does anyone know where I can find the launcher logs? Also can you guys get into HOI4 by bypassing the launcher on startup?

I am using Manjaro Linux, Proton 8.0-4, and the 6.1.55 Linux kernel.
 
@laurensb - Interesting. Even though we don't officially support the flatpak'ed version, the launcher works just fine under flatpak on several of my personal computers with both AMD and NVidia GPU:s. We are receiving reports that some Linux players are experiencing problems, but have as of yet not been able to pin down exactly what is causing them.

So maybe time for a longshot: What type of GPU and drivers are you running?
I have both a laptop and desktop with AMD GPUs, and use the "amdgpu" video driver.
 
2023-11-03T20:46:24.389Z (pid:12393) error [main]: Renderer process is gone: crashed 2023-11-03T20:46:24.389Z (pid:12393) info [main]: Trying to relaunch without hardware acceleration 2023-11-03T20:46:24.438Z (pid:12393) warn [GfnService]: Failed to close GeforceNow runtime
I posted a bug report with the full log, but I can confirm I have the same lines in the end than you. So maybe this runs even deeper?
 
I posted a bug report with the full log, but I can confirm I have the same lines in the end than you. So maybe this runs even deeper?
Where did you post that bugreport? I only found this thread with logs in your history, but none of the log files which you posted there contain lines like [44933:1103/001603.583387:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!. I'm asking how you got the lines, because I want to test if they are related. If all systems which have the crash show the line and if it is not present on systems which don't have the crash, it is likely related. But if the line is also present on systems which don't have the crash or if only some crashing systems have it, then it is probably unrelated(like the libva error which I got).
 
I am having the same issue, the Paradox launcher opens, the closes and reopens, and then closes again. This started happening on my laptop, but started on my computer like a day later. Does anyone know where I can find the launcher logs? Also can you guys get into HOI4 by bypassing the launcher on startup?

I am using Manjaro Linux, Proton 8.0-4, and the 6.1.55 Linux kernel.
Are you using proton for hoi4? I thought that the windows version of the launcher was not affected by this crash.

You can find the log files in "$XDG_DATA_HOME/Paradox Interactive/launcher-v2" (if $XDG_DATA_HOME is set) or in "~/.local/share/Paradox Interactive/launcher-v2" (if it is not set).
 
Workarounds
Since more and more people arrive in this thread and not everybody read the other recent launcher threads, I think it is useful to list the workarounds which can be used until a fixed version of the launcher is released:
  • click fast enough so that you can start the game before the launcher crashes. It might help to move the mouse out of the launcher window immediately afterwards, because mouse movements in the window seem to hasten the crash(but I might be imagining this)
  • return to an old launcher version which still works. You can do that by either deleting "~/.paradoxlauncher/launcher-v2.2023.14/" or doing a full reinstall of the launcher as explained in this support document. But the launcher will try to update itself again. There are a few ways to avoid this:
    • copy the folder of a working launcher version in ~/.paradoxlauncher to ~/.paradoxlauncher/launcher-v2.2099.99 .It basically makes the bootstrapper(the launcher for the launcher) start the launcher from that folder, because it assumes that this is the newest version. The launcher then downloads an update into launcher-v2.2023.14 and tells you that it updated, but this will never get started. But you will always be greeted by the message that an update has been installed(but I think it doesn't install again)
    • remove write permissions from ~/.paradoxlauncher (e.g. with chmod a-w ~/.paradoxlauncher ). This will lead to regular update-failed messages
    • use some script to always remove the launcher-v2.2023.14 folder
  • if you did the full launcher uninstall from the previous step, you will get whichever launcher version is shipped with your game. Some of them are quite old(e.g. eu4 has 2022.9 ). To get a more recent version, you could try a different game or download version 2023.13 from https://launcher.paradoxinteractive.com/v2/paradox-launcher-installer-2023_13.deb and then either install+start it(if you are on a .deb based distro like ubuntu) or unpack the file "launcher-installer-linux_2023.13" from it(e.g. with dpkg-deb --fsys-tarfile paradox-launcher-installer-2023_13.deb |tar x --strip-components=4 "./opt/Paradox Interactive/Paradox Launcher v2/launcher-installer-linux_2023.13" and run that file
  • use the windows version of the game with proton
  • start the game from the command line to bypass the launcher. Steam must be running in the background. Some games will have trouble with DLCs and achievements if they are started in this way. To fix that, you can provide the steam app id of the game on the command line. For eu4 the following command works(if executed from the folder where eu4 is installed): SteamAppId="236850" ./eu4
  • configure steam to run the game directly without the launcher. Some games have that as a launch option(e.g. hoi4) and for others you can change the launch options to ./eu4 %command% (replace "./eu4" with the location of the game executable relative to the installation folder (e.g. "./binaries/victoria3" for vic3)).
If you use one of the workarounds which involve changing files or launch options, I would recommend that you write down what you did, so that you can undo it when the launcher problem has been fixed.
 
  • 5
  • 2Like
Reactions:
Workarounds
  • click fast enough so that you can start the game before the launcher crashes. It might help to move the mouse out of the launcher window immediately afterwards,
This does work. Through the mid of the loading screen you will be send back to the desktop and see the crash report window for the launcher. Don't click it to close or anything and just click the tab of the game. Otherwise the game closes too.
 
Through the mid of the loading screen you will be send back to the desktop and see the crash report window for the launcher.
Is this for stellaris? That crash reporter is for some part of stellaris which is crashing on startup. That problem is separate from the launcher problem and has happened since a recent update(also with older launcher versions). There is at least one bugreport in the stellaris bugreports forum about this.
 
Does the Windows version of the launcher work on Linux? Also I rolled back my PC and started HOI4 without internet and the launcher was fine, after I turned on internet the launcher got an update, right after the update it started doing this. I'm 99% sure this was caused by an update.
 
Oh my gosh, I was going crazy thinking this was an update on my end, but rolling back manually to 2023.13 (and one `chmod -R ugo-w ~/.paradoxlauncher` later to remove its own write permissions so it stops downloading 2023.14) works fine. This is definitely a regression from 2023.13 -> 2023.14 on Linux.
 
Where did you post that bugreport? I only found this thread with logs in your history, but none of the log files which you posted there contain lines like [44933:1103/001603.583387:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!. I'm asking how you got the lines, because I want to test if they are related. If all systems which have the crash show the line and if it is not present on systems which don't have the crash, it is likely related. But if the line is also present on systems which don't have the crash or if only some crashing systems have it, then it is probably unrelated(like the libva error which I got).
 
Workarounds
Since more and more people arrive in this thread and not everybody read the other recent launcher threads, I think it is useful to list the workarounds which can be used until a fixed version of the launcher is released:
  • ....
  • use the windows version of the game with proton
  • ....
If you use one of the workarounds which involve changing files or launch options, I would recommend that you write down what you did, so that you can undo it when the launcher problem has been fixed.

I want to add here it is important to set -opengl in the launch options when playing with Proton as the game will crash without it.
Also Multiplayer is borked when you not use the Store independent Multiplayer Mode (aka Nakama)
 
Does the Windows version of the launcher work on Linux? Also I rolled back my PC and started HOI4 without internet and the launcher was fine, after I turned on internet the launcher got an update, right after the update it started doing this. I'm 99% sure this was caused by an update.
You can use proton to run the windows version of the game and the launcher(depending on the game you might need more steps to get it working). But it would be difficult to run the windows version of the launcher together with the linux version of the game.
I want to add here it is important to set -opengl in the launch options when playing with Proton as the game will crash without it.
Also Multiplayer is borked when you not use the Store independent Multiplayer Mode (aka Nakama)
Which game are you talking about and for which proton version does that apply? At least with proton 8.04, the windows version of eu4 doesn't start with the -opengl option, but it works fine without it(though I have not tested MP).

That's the thread which I already found. But the logs which you posted there don't contain these lines and they don't explain how you started the launcher on the command line to get those lines.
 
I had the start problems, but executing the game from the folder without the launcher works well.
On of the possible problems on my PC, are related to non compatible mods.
 
Update: We managed to get a repro case internally and have confirmed that the fix we have works - at least for that machine! A hotfix will be forthcoming when it's been run through the standard testing procedures.
 
  • 4Like
  • 3
Reactions: