Home Trending Latest threads New posts Developer diaries

[Linux] Crash at startup (3.9.3)

Jump to latest Follow Reply
  • 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.
Stellaris 53998 Bug Reports 37255 Console edition 1311 Suggestions 21646 Tech Support 3199 Multiplayer 392 User Mods 4791 Stellaris AAR (After Action Reports)
Reporting in form Arch linux with NVIDIA GPU, seeing same issue, but core of problem seems to be between game and steam, if I launch the launcher manually with out steam game seems to comes up fine. not certain what all is missing with out or how to verify that all purchased content is working separate from steam, but I can play my local saved games.

bin/sh /home/yourusername/.paradoxlauncher/launcher-v2.2023.14/Paradox Launcher --pdxlSessionId 4000000b-0000-0000-0000-a0000000000e --pdxlGameDir /data/SteamLibrary/steamapps/common/Stellaris --gameDir /data/SteamLibrary/steamapps/common/Stellaris

the pdxlSessionId might be unique per user but the bogus one I made up here seemed to work so it might be part of the steam interactions

This seems like the best option as trying to change out CrashReporter did nto work very well, all you loose here seems to be steam interaction,
 
I'm using OpenSuse Kernel 6.5.9-1 and still not work. I discovered that Linux just work with Steam Compatibility Proton, enabling it should work fine. But for a game that worked flawless in Linux is a shame that I have to come back to compatibility mode to work. Even CK3 is working normally without compatibility on my Linux.

And until now we don't have any news of a Bug Fix or a future Patch Note that will Fix this issue.
 
  • 1Like
Reactions:
Nak'Arosh said:
I'm using OpenSuse Kernel 6.5.9-1 and still not work. I discovered that Linux just work with Steam Compatibility Proton, enabling it should work fine. But for a game that worked flawless in Linux is a shame that I have to come back to compatibility mode to work. Even CK3 is working normally without compatibility on my Linux.

And until now we don't have any news of a Bug Fix or a future Patch Note that will Fix this issue.
Click to expand...
Actually we do - IF your issue is the launcher bug. You should now be on version 2023.14.1 which is a specific fix for that.

If however you have a game problem, that's a different issue.
 
I have the same problem on 64-bit Arch Linux updated daily. I was able to update the launcher to version 2023.14.1, but the game (ver. 3.9.3.) crashes before getting to the main menu.
When launching the game directly from console I get

$ ./stellaris
[systemsettings.cpp:44] CPU Model: 13th Gen Intel(R) Core(TM) i9-13980HX

[systemsettings.cpp:45] CPU Speed: 2200MHz

[systemsettings.cpp:46] CPU Physical Cores: 24

[systemsettings.cpp:47] CPU Logical Cores: 32

[systemsettings.cpp:48] System Memory: 63999

[systemsettings.cpp:49] OS: Linux;6.6.1-arch1-1;#1 SMP PREEMPT_DYNAMIC Wed, 08 Nov 2023 16:05:38 +0000;x86_64

[systemsettings.cpp:50] OS Language:

[S_API] SteamAPI_Init(): Loaded '/home/zbigniew/.local/share/Steam/linux64/steamclient.so' OK.
Setting breakpad minidump AppID = 281990
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198021539650 [API loaded no]
[virtualfilesystem_physfs.cpp:339] Failed to mount /home/zbigniew/.local/share/Steam/steamapps/common/Stellaris/dlc/dlc004_plantoid/dlc004.zip with error unsupported

[virtualfilesystem_physfs.cpp:339] Failed to mount /home/zbigniew/.local/share/Steam/steamapps/common/Stellaris/dlc/dlc013_horizon_signal/dlc013.zip with error unsupported

[virtualfilesystem_physfs.cpp:339] Failed to mount /home/zbigniew/.local/share/Steam/steamapps/common/Stellaris/dlc/dlc030_paragon/dlc030.zip with error unsupported

[virtualfilesystem_physfs.cpp:339] Failed to mount /home/zbigniew/.local/share/Steam/steamapps/common/Stellaris/dlc/dlc029_firstcontact/dlc029.zip with error unsupported

[virtualfilesystem_physfs.cpp:339] Failed to mount /home/zbigniew/.local/share/Steam/steamapps/common/Stellaris/dlc/dlc002_arachnoid/dlc002.zip with error unsupported

[virtualfilesystem_physfs.cpp:339] Failed to mount /home/zbigniew/.local/share/Steam/steamapps/common/Stellaris/dlc/dlc015_anniversary/dlc015.zip with error unsupported

Trying to Write minidump to dir: /home/zbigniew/.local/share/Paradox Interactive/Stellaris/crashes/stellaris_20231110_222835/
Created Minidump: /home/zbigniew/.local/share/Paradox Interactive/Stellaris/crashes/stellaris_20231110_222835//8f9849e6-6629-468d-070889b0-c7ebdcc3.dmp

(CrashReporter:325555): Gtk-WARNING **: 22:28:35.514: Negative content height -9 (allocation 1, extents 5x5) while allocating gadget (node scrollbar, owner GtkScrollbar)

(CrashReporter:325555): Gtk-CRITICAL **: 22:28:35.514: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(CrashReporter:325555): Gtk-WARNING **: 22:28:35.516: Negative content height -3 (allocation 7, extents 5x5) while allocating gadget (node scrollbar, owner GtkScrollbar)

(CrashReporter:325555): Gtk-CRITICAL **: 22:28:35.516: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar
Click to expand...

Strangely enough the game can be successfully launched with root privileges

$ sudo ./stellaris
[sudo] hasło użytkownika zbigniew:
[systemsettings.cpp:44] CPU Model: 13th Gen Intel(R) Core(TM) i9-13980HX

[systemsettings.cpp:45] CPU Speed: 5600MHz

[systemsettings.cpp:46] CPU Physical Cores: 24

[systemsettings.cpp:47] CPU Logical Cores: 32

[systemsettings.cpp:48] System Memory: 63999

[systemsettings.cpp:49] OS: Linux;6.6.1-arch1-1;#1 SMP PREEMPT_DYNAMIC Wed, 08 Nov 2023 16:05:38 +0000;x86_64

[systemsettings.cpp:50] OS Language:

[S_API] SteamAPI_Init(): SteamAPI_IsSteamRunning() did not locate a running instance of Steam.
dlopen failed trying to load:
/root/.steam/sdk64/steamclient.so
with error:
/root/.steam/sdk64/steamclient.so: cannot open shared object file: No such file or directory
[S_API] SteamAPI_Init(): Sys_LoadModule failed to load: /root/.steam/sdk64/steamclient.so
[S_API] SteamAPI_Init(): SteamAPI_IsSteamRunning() did not locate a running instance of Steam.
dlopen failed trying to load:
/root/.steam/sdk64/steamclient.so
with error:
/root/.steam/sdk64/steamclient.so: cannot open shared object file: No such file or directory
[S_API] SteamAPI_Init(): Sys_LoadModule failed to load: /root/.steam/sdk64/steamclient.so
[S_API] SteamAPI_Init(): SteamAPI_IsSteamRunning() did not locate a running instance of Steam.
dlopen failed trying to load:
/root/.steam/sdk64/steamclient.so
with error:
/root/.steam/sdk64/steamclient.so: cannot open shared object file: No such file or directory
[S_API] SteamAPI_Init(): Sys_LoadModule failed to load: /root/.steam/sdk64/steamclient.so
[S_API] SteamAPI_Init(): SteamAPI_IsSteamRunning() did not locate a running instance of Steam.
dlopen failed trying to load:
/root/.steam/sdk64/steamclient.so
with error:
/root/.steam/sdk64/steamclient.so: cannot open shared object file: No such file or directory
[S_API] SteamAPI_Init(): Sys_LoadModule failed to load: /root/.steam/sdk64/steamclient.so
[S_API] SteamAPI_Init(): SteamAPI_IsSteamRunning() did not locate a running instance of Steam.
dlopen failed trying to load:
/root/.steam/sdk64/steamclient.so
with error:
/root/.steam/sdk64/steamclient.so: cannot open shared object file: No such file or directory
[S_API] SteamAPI_Init(): Sys_LoadModule failed to load: /root/.steam/sdk64/steamclient.so
ALSA lib pcm_dmix.c:1000:(snd_pcm_dmix_open) unable to open slave
[S_API] SteamAPI_Init(): SteamAPI_IsSteamRunning() did not locate a running instance of Steam.
dlopen failed trying to load:
/root/.steam/sdk64/steamclient.so
with error:
/root/.steam/sdk64/steamclient.so: cannot open shared object file: No such file or directory
[S_API] SteamAPI_Init(): Sys_LoadModule failed to load: /root/.steam/sdk64/steamclient.so
Click to expand...

Rolling back from current version 3.9.3. to the previous branch 3.8.4 makes the game playable again on a non-root user account.
Hopefully version 3.10.0 will be introduced with the fix.
 
After the game starts game says Disconnected and a Crash popup appears.

Crash reports attached on reports.zip and steam launch log attached on steam.log
 

Attachments

  • reports.zip
    382 bytes · Views: 0
  • steam.log
    11,4 KB · Views: 0
As with so many others, I am also suffering crashes when I try to run Stellaris 3.9.3 or 3.10 - 3.8.4 and below it works fine. No mods, flatpack steam client, Linux Mint 21.2.

Regards,

fasquardon
 
  • 2
Reactions:
For me on Arch Linux both native and Windows versions after 3.10 update sometimes crash on "Loading Map Graphics". Also I always have crash reporter right after game launches, but it is continues to work.

Also Windows version (Tested Proton 8.0 and GE, Experimental doesn't work) looks like this, background and some images (like human here) doesn't load:

1700384531276.png
 
Kepos said:
First idea: Is PDX trying to fish for telemetry data...not unlike Epic once did and lost a huge bunch of their Steam players?
Click to expand...
PDX games routinely send telemetry back but it's purely in-game stuff e.g. what sort of galaxy is chosen, whether you're a prescripted or custom empire, how long a play session lasts etc. etc.
 
I think I figured out this one. With debian stable stellaris 3.9.3 works but after securtiy updates I get the bug described here. After examining all security updates I found the problematic packages are xserver-xorg-core (and xserver-common). So this actually is an xorg bug, and not a stellaris bug. For those who want to try xserver-xorg-core from debian stable in version 2:21.1.7-3 works fine.

Edit: Now I cannot reproduce this behaviour anymore. Stellaris works now in debian stable even if the security updates are installed ...

Edit2: Now I managed to reproduce the bug on debian stable by using the libstdc++6 package from debian testing. Debian stable has libstdc++6 in version 12.2.0 while debian testing has version 13.2.0. Perhaps this is an issue with libstdc++?
 
Last edited:
I have Manjaro Linux, and the same issue also happens in my case. Version 3.8.4 and below works fine. As mentioned above, this appears to be an issue with libstdc++, possibly with ABI.

I found that I can work around it by running Stellaris with Proton 8.0-4 (latest). With default settings game launches with missing textures (gray graphics), but this can be fixed by reverting back to DirectX9. I have not experienced any issues so far with this workaround. I found somewhere that Proton has some trouble handling more recent versions of DirectX, so maybe this is the cause of the gray graphics problem.

To apply this workaround :

  1. Open game settings by clicking on the little gear on the game page (steam library) in the Steam tool.
  2. Go to the "compatibility" tab, check "Force the use of a specific Steam Play compatibility tool" then select the latest Proton version.
  3. Go to "General" and put "-dx9" in LAUNCH OPTIONS.

Strangely enough the game can be successfully launched with root privileges
Click to expand...

I'm a little bit late to the party, but here is some likely explanation.

It is because when something is launched as root on Linux, the home folder is set to /root. According to the console output, during startup, the game is trying to load some shared library called "steamclient.so" (presumably with some steam integration stuff) from ".steam/sdk64" which is located in the home directory of the steam user.

Now, the stack trace contains: "NAdditionalContent::CAdditionalContentMetadataVisitor" method; the name suggests that it likely loads DLC content or something like that. Most likely, the game works when running as root because it cannot connect to Steam (no steamclient.so), and this code does not get called. The same effect can be achieved by shutting down Steam and running the executable directly (this does not start Steam). Unfortunately, it also causes no DLCs or mods to load, which is a non-starter for me.

So, for now, it seems that the options for running the latest version of Stellaris on Linux are as follows:
  1. Use the system with libstdc++6 version 12.2.0 or older (I didn't test this one).
  2. Launch the executable directly with Steam switched off and play the game without any mods or DLCs.
  3. Use proton with DirectX9.
 
  • 1Like
Reactions:
Same here:
Code: 
Application: Stellaris
Version: 3.10.1
Date/Time: 2023-11-29 01:31:10

Caught signal 11 (SIGSEGV)

Original Stack Trace:
  /usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6(_ZNKSt7__cxx118time_getIcSt19istreambuf_iteratorIcSt11char_traitsIcEEE3getES4_S4_RSt8ios_baseRSt12_Ios_IostateP2tmPKcSD_+0xc6) [0x7feefde95836]
  /home/rincat/.SteamLibrary/MS/steamapps/common/Stellaris/stellaris(_ZStrsIcSt11char_traitsIcEERSt13basic_istreamIT_T0_ES6_St9_Get_timeIS3_E+0xae) [0x17cf49e]
  /home/rincat/.SteamLibrary/MS/steamapps/common/Stellaris/stellaris(_ZN18NAdditionalContent33CAdditionalContentMetadataVisitor11VisitObjectERNS_26SAdditionalContentMetadataEN12NJSONVisitor14CObjectEntriesE+0x346) [0x17c50a6]
  /home/rincat/.SteamLibrary/MS/steamapps/common/Stellaris/stellaris(_ZN12NJSONVisitor5ParseIN18NAdditionalContent26SAdditionalContentMetadataEEEvRT_RK7CStringRNS_8CVisitorIS3_EE+0x2e) [0x17bee9e]
  /home/rincat/.SteamLibrary/MS/steamapps/common/Stellaris/stellaris() [0x17b977f]
  /home/rincat/.SteamLibrary/MS/steamapps/common/Stellaris/stellaris(_ZN11CTaskThread3RunEv+0x138) [0x30e2598]
  /home/rincat/.SteamLibrary/MS/steamapps/common/Stellaris/stellaris(_ZN11CTaskThread3RunEPv+0x6) [0x30e2456]
  /usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6(+0xe41e3) [0x7feefde691e3]
  /lib64/libc.so.6(+0x8516c) [0x7feefdc3416c]
  /lib64/libc.so.6(+0x1058dc) [0x7feefdcb48dc]

Demangled Stack Trace:
  /usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6 ( std::__cxx11::time_get<char, std::istreambuf_iterator<char, std::char_traits<char> > >::get(std::istreambuf_iterator<char, std::char_traits<char> >, std::istreambuf_iterator<char, std::char_traits<char> >, std::ios_base&, std::_Ios_Iostate&, tm*, char const*, char const*) const  + 0xc6  )  [0x7feefde95836]
  /home/rincat/.SteamLibrary/MS/steamapps/common/Stellaris/stellaris ( std::basic_istream<char, std::char_traits<char> >& std::operator>><char, std::char_traits<char> >(std::basic_istream<char, std::char_traits<char> >&, std::_Get_time<char>)  + 0xae  )  [0x17cf49e]
  /home/rincat/.SteamLibrary/MS/steamapps/common/Stellaris/stellaris ( NAdditionalContent::CAdditionalContentMetadataVisitor::VisitObject(NAdditionalContent::SAdditionalContentMetadata&, NJSONVisitor::CObjectEntries)  + 0x346 )  [0x17c50a6]
  /home/rincat/.SteamLibrary/MS/steamapps/common/Stellaris/stellaris ( void NJSONVisitor::Parse<NAdditionalContent::SAdditionalContentMetadata>(NAdditionalContent::SAdditionalContentMetadata&, CString const&, NJSONVisitor::CVisitor<NAdditionalContent::SAdditionalContentMetadata>&)  + 0x2e  )  [0x17bee9e]
  /home/rincat/.SteamLibrary/MS/steamapps/common/Stellaris/stellaris (                                                   )  [0x17b977f]
  /home/rincat/.SteamLibrary/MS/steamapps/common/Stellaris/stellaris ( CTaskThread::Run()                        + 0x138 )  [0x30e2598]
  /home/rincat/.SteamLibrary/MS/steamapps/common/Stellaris/stellaris ( CTaskThread::Run(void*)                   + 0x6   )  [0x30e2456]
  /usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6 (                                           + 0xe41e3)  [0x7feefde691e3]
  /lib64/libc.so.6               (                                           + 0x8516c)  [0x7feefdc3416c]
  /lib64/libc.so.6               (                                           + 0x1058dc)  [0x7feefdcb48dc]

Seems related to time_get function, maybe paradox could try GCC 12.3?
 
AndrewT said:
Actually we do - IF your issue is the launcher bug. You should now be on version 2023.14.1 which is a specific fix for that.

If however you have a game problem, that's a different issue.
Click to expand...
My brother, I will kindly tell you that none of the recent nor the previous "solutions" have worked on my extend, the game become unplayable, the devs don't care about the Linux playbase, and at this point we all should get over it and try something else.
 
CapitanOctopus said:
My brother, I will kindly tell you that none of the recent nor the previous "solutions" have worked on my extend, the game become unplayable, the devs don't care about the Linux playbase, and at this point we all should get over it and try something else.
Click to expand...

Unfortunately, supporting native software for Linux is a massive pain in the lower level. That's because unlike Windows, where most people use win11 or win10, Linux has a dozen, sometimes wildly different distributions. As a result, you get varying versions of essential components (like glibc, graphics drivers, and so on). Also, there are different versions of each Linux distro. And, of course, people apply their tweaks on top of the basic installation. So, it is essentially impossible to test for all configurations on Linux. It is already very hard or impossible on Windows (you can't test for all the hardware configurations), but then on Linux, you get many more dimensions of the configuration space. Most Linux-compatible software is released and tested on major distros (like Ubuntu), and then it is up to volunteers to prepare and maintain packages for less popular distributions. Of course, you can't do that with a closed-source game like Stellaris. Valve has recently been doing some great work with its proton software, but there is still some work to be done in this regard. I am also frustrated when the software that I paid for suddenly stops working, but I also understand the developers' perspective. I would expect Linux support priorities to lie with supporting Steam OS (Linux arch derivative) since this is what Steam Deck uses.
 
Last edited:
CapitanOctopus said:
My brother, I will kindly tell you that none of the recent nor the previous "solutions" have worked on my extend, the game become unplayable, the devs don't care about the Linux playbase, and at this point we all should get over it and try something else.
Click to expand...
Is yours a launcher or game problem please?

As to not caring, in the patch notes for 3.10.2 the devs have specifically stated they are working on Linux fixes, AND give there workarounds for the 2 most common Linux issues.
 
You must log in or register to reply here.
Top Bottom
Back