Stellaris creashes at 81% during startup at loading screen since version 2.8 [Linux]

[Tommy[D]]

Description
Stellaris creashes at 81% during startup at loading screen since version 2.8

Game Version
3.0.2

What version do you use?
Steam

What expansions do you have installed?
Synthetic Dawn, Utopia, Leviathans Story Pack, Apocalypse, Megacorp, Distant Stars, Ancient Relics

Do you have mods enabled?
No

Please explain your issue is in as much detail as possible.
When i try to start the game, the loading screen comes up, goes to 81% and stops there. In the background the crash reporter opens and once i close that window, the game closes too.

Steps to reproduce the issue.
Klick "play" in the paradox launcher

 

[AndrewT]

Looks like you're on Linux, is that right? What distro?

Game Version
3.0.2

You've opted into an older version, is that right? Does 3.1.1 work any better?

ANyway we see a LOT of bad errors in that log, so let's start with a clean reinstall:

- move any valued save games elsewhere, and user_empire_designs.txt from /Documents/Paradox Interactive/Stellaris/ if you have made any custom empires or races.
- "uninstall" in Steam-Stellaris
- manually delete both the Steam/SteamApps/common/Stellaris AND Documents/Paradox Interactive/Stellaris folders
- re-install game in Steam, run a Steam Verify when done.
- start the game with no mods active and test

In particular you need to make sure there are no files or folders left under either the Steam Stellaris or Documents Stellaris locations, before installing again.

Linux file locations are documented in the Sticky thread above.


If you still get this problem after that:

Please attach here your Documents/Paradox Interactive/Stellaris/settings.txt and pdx_settings.txt .
From your Documents/Paradox Interactive/Stellaris/logs/ folder, attach here system.log , error.log .

Also in Steam please click on Steam-Help-System Info, and paste everything there into a text file and attach that here.

 

[Tommy[D]]

Looks like you're on Linux, is that right? What distro?

Gentoo Linux

You've opted into an older version, is that right? Does 3.1.1 work any better?

3.0.2 was the actual version when i did the last test (and the crash report should be from that version)

ANyway we see a LOT of bad errors in that log, so let's start with a clean reinstall:

- move any valued save games elsewhere, and user_empire_designs.txt from /Documents/Paradox Interactive/Stellaris/ if you have made any custom empires or races.

- "uninstall" in Steam-Stellaris
- manually delete both the Steam/SteamApps/common/Stellaris AND Documents/Paradox Interactive/Stellaris folders
- re-install game in Steam, run a Steam Verify when done.
- start the game with no mods active and test

done and same result

In particular you need to make sure there are no files or folders left under either the Steam Stellaris or Documents Stellaris locations, before installing again.

Linux file locations are documented in the Sticky thread above.


If you still get this problem after that:

Please attach here your Documents/Paradox Interactive/Stellaris/settings.txt and pdx_settings.txt .
From your Documents/Paradox Interactive/Stellaris/logs/ folder, attach here system.log , error.log .

Also in Steam please click on Steam-Help-System Info, and paste everything there into a text file and attach that here.

done

 

[AndrewT]

FYI the only supported distro is Ubuntu.

3.0.2 was the actual version when i did the last test (and the crash report should be from that version)

If you run it now does the launcher show 3.1.1 ?


Lots of errors in that log but really nothing that explains the hang at 81%. We have seen that happen on Windows with some devices attached like joysticks or game controllers. I haven't seen that under Linux or Mac, but if you have anything like that, try unplugging it.

 

[Tommy[D]]

FYI the only supported distro is Ubuntu.


If you run it now does the launcher show 3.1.1 ?

The launcher now shows Lem v3.1.1 (22a5)

Lots of errors in that log but really nothing that explains the hang at 81%. We have seen that happen on Windows with some devices attached like joysticks or game controllers. I haven't seen that under Linux or Mac, but if you have anything like that, try unplugging it.

I only have keyboard, mouse and 2 sound devices for in- and output. Since i can still go back to 2.7 and it still works, this seems to be an internal issue introduced with 2.8. But since the game does not output any helpful details or logs, i have no clue what the actual issue may be.

 

[AndrewT]

I agree it looks like that, but OTOH we would know if no Linux player could run the game since the 2.8 patch!

If you run the Stellaris executable from a command line, is there any useful output shown there leading up to the crash, or after it? How about in any Linux OS logs?

 

[Tommy[D]]

I agree it looks like that, but OTOH we would know if no Linux player could run the game since the 2.8 patch!

If you run the Stellaris executable from a command line, is there any useful output shown there leading up to the crash, or after it? How about in any Linux OS logs?

Nothing interesting running from command line, just tells some system details, connects to steam, dumps the crash minidump. Also nothing in the OS logs either.

As i said: pretty hard to debug something that does not give any useful output.

With no useful information i cannot even try to debug this myself, might be an issue with the specific set of DLCs, might be an issue with specific system libs, might be an issue with specific DLCs with specific system libs....without any useful output from the game before/during/after crash, i can only report this.

 

[AndrewT]

Hmmm, really not sure where to go from here, as you say we have no clues whatsoever as to even the general area of the problem.

Are you wedded to Gentoo, would you consider Ubuntu?

 

[Tommy[D]]

Hmmm, really not sure where to go from here, as you say we have no clues whatsoever as to even the general area of the problem.

Are you wedded to Gentoo, would you consider Ubuntu?

I wont switch from Gentoo. Also please keep in mind that the main difference is the tools to install programs, so chances are slim that this is an os-specific issue.

Even without debugging symbols in stellaris, i am getting the following backtrace when running it inside gdb (after it segfaulted):

#0  0x0000000000e3324f in SFlagTexture::operator=(SFlagTexture const&) ()
#1  0x0000000000e2dd4e in ?? ()
#2  0x0000000000e31bac in CEmpireFlagDatabase::Init() ()
#3  0x0000000000e4fefa in CGameApplication::InitGame() ()
#4  0x0000000000e4b12d in CGameApplication::Init() ()
#5  0x0000000000df9955 in RunGame(int, char**) ()
#6  0x0000000000df40dc in main ()

Running it with strace gives the following last lines:

openat(AT_FDCWD, "/home/thomas/.local/share/Steam/steamapps/common/Stellaris/flags/special/abandoned.dds", O_RDONLY) = 47
fstat(47, {st_mode=S_IFREG|0755, st_size=5312, ...}) = 0
fstat(47, {st_mode=S_IFREG|0755, st_size=5312, ...}) = 0
read(47, "DDS |\0\0\0\7\20\10\0$\0\0\0$\0\0\0@\24\0\0\0\0\0\0\0\0\0\0"..., 16384) = 5312
close(47)                               = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
rt_sigaction(SIGSEGV, NULL, {sa_handler=0x7f6577ed2dc0, sa_mask=[ILL ABRT BUS FPE SEGV], sa_flags=SA_RESTORER|SA_ONSTACK|SA_SIGINFO, sa_restorer=0x7f657c11b750}, 8) = 0
getpid()                                = 23397
rt_sigaction(SIGSEGV, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f657c11b750}, NULL, 8) = 0
rt_sigaction(SIGABRT, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f657c11b750}, NULL, 8) = 0
rt_sigaction(SIGFPE, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f657c11b750}, NULL, 8) = 0
rt_sigaction(SIGILL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f657c11b750}, NULL, 8) = 0
rt_sigaction(SIGBUS, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f657c11b750}, NULL, 8) = 0
rt_sigreturn({mask=[]})                 = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
+++ killed by SIGSEGV +++
Segmentation fault

It did not access any none-game related files for pages before that, so the issue is most likely within the game binary or game files.

 

[AndrewT]

openat(AT_FDCWD, "/home/thomas/.local/share/Steam/steamapps/common/Stellaris/flags/special/abandoned.dds", O_RDONLY) = 47

Do I read this line correctly, that file is read only? Not that that should cause a segfault, but still ...

What file system are the game and its Documents folders on? Just standard EXT4 or something more exotic?

 

[Tommy[D]]

Do I read this line correctly, that file is read only? Not that that should cause a segfault, but still ...

What file system are the game and its Documents folders on? Just standard EXT4 or something more exotic?

I have attached the full strace output, compressed since the output itself is around 26MB.

I have full read/write/execute-access to that file, so there is no limitation from the filesystem. Seems more like stellaris itself does limit the access to only reading the file. Looks also rather strange, that every file has the executable-bit, including text files, but that is a different topic and should not cause issues in this case.

File system is a standard reiserfs.

 

[AndrewT]

As you say I see no further information in there as to what might be causing this. It's clearly not a game bug or all Linux players would get it, so despite your inclination otherwise I think this is an issue with this distro, or at least this specific installation of it.

You could try the -debug launch option in Steam or on the command line, I think that might log more info in some extra log files; that said I haven't tried it with Linux!

Also, do you have any access to Linux or Gentoo support resources who might be able to help from the OS perspective?

 

[Tommy[D]]

As you say I see no further information in there as to what might be causing this. It's clearly not a game bug or all Linux players would get it, so despite your inclination otherwise I think this is an issue with this distro, or at least this specific installation of it.

You could try the -debug launch option in Steam or on the command line, I think that might log more info in some extra log files; that said I haven't tried it with Linux!

Also, do you have any access to Linux or Gentoo support resources who might be able to help from the OS perspective?

I now tried an arch linux based livecd and tried starting stellaris with that, result is exactly the same. So that does rule out any specific details with my installation.

The -debug option does not seem to add any additional info. Would actually be good if stellaris could have more details/debugging output.

 

[AndrewT]

Would actually be good if stellaris could have more details/debugging output.

I can only agree!

I now tried an arch linux based livecd and tried starting stellaris with that, result is exactly the same. So that does rule out any specific details with my installation.

Does running it from a command line there show anything useful?

Is there a way of doing this with Ubuntu instead of Arch?

 

[Tommy[D]]

Does running it from a command line there show anything useful?

I dont have the log, but from my memory it looked at least very similar to the output on Gentoo Linux. The error.log and other logs also look the same.

Is there a way of doing this with Ubuntu instead of Arch?

There is probably a way, would have to check during the weekend, but i dont expect any other outcome.

 

[AndrewT]

The upside is if it fails on Ubuntu., that's a supported platform and I can escalate the issue if it comes to that. 16.04 and above are supported versions.

 

[sebastinas]

I am able to reproduce the issue on Ubuntu 20.04 with a NVIDIA GPU (with the 470 drivers). I have the exact same error as reported by the others in this thread.

FWIW, Stellaris launches (I didn't tried anything else) on an Ubuntu 20.04 with an Intel GPU.

 

[AndrewT]

I just tried the game on my VM of Ubuntu 21.04 and it worked perfectly.

So you may well be right and this is an issue with those nVidia drivers, as obviously my VM uses an emulated GPU even weaker than that Intel.

Is there any way you can try this with older versions of that driver?

 

[Tommy[D]]

The upside is if it fails on Ubuntu., that's a supported platform and I can escalate the issue if it comes to that. 16.04 and above are supported versions.

I tried it with the LTS version of Ubuntu from the live cd and the result is exactly the same: It crashes at the loading screen at 81%. If needed, i can upload the logs again, but the content is basicly the same (it obviously now says Ubuntu instead of Gentoo, but there are no other error messages).

 

[Tommy[D]]

I just tried the game on my VM of Ubuntu 21.04 and it worked perfectly.

So you may well be right and this is an issue with those nVidia drivers, as obviously my VM uses an emulated GPU even weaker than that Intel.

Is there any way you can try this with older versions of that driver?

I already had the crash when 2.8 came out about a year ago, so i was using an older version of the nvidia driver (back then it was the 455 series).

edit: I even tried it with the ancient version 390.144 and got the same result. So it seems like 2.8 introduced an issue with nvidia graphic cards or drivers.