• 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.

zubozrout

Second Lieutenant
18 Badges
Oct 6, 2012
110
175
  • Cities in Motion 2
  • Crusader Kings II
  • Cities in Motion
  • Cities: Skylines Deluxe Edition
  • Cities: Skylines - Campus
  • Cities: Skylines Industries
  • Cities: Skylines - Parklife
  • Cities: Skylines - Parklife Pre-Order
  • Cities: Skylines - Green Cities
  • Cities: Skylines - Mass Transit
  • Cities: Skylines - Natural Disasters
  • Cities: Skylines - Snowfall
  • Cities: Skylines - After Dark
  • Cities: Skylines
  • Heir to the Throne
  • Divine Wind
  • Europa Universalis III: Chronicles
  • Europa Universalis III

Information​

I have disabled all mods​

Yes

Required​

Summary​

The game fails loading the second time or later after first install with a libmono.so crash (exit code 134)

Expected Result​

The game launches just fine.

Actual Result​

The game fails to load, but interestingly it does load the first time it is installed (I always clear game files). The second time (even without restarting Steam) it starts failing.

Steps to reproduce​

Considering I am likely the only one having this particular issue as I haven't seen such a report IDK. The steps are to install the game, run, stop, retry and it fails on my end.

Platform​

Steam

Game Version​

Launcher 2024.16, Game 1.18.1-f3

Optional​

Description​

Hi,
Recently the game stopped working for me. I've been playing it just fine up until maybe 3 weeks ago, when some Steam (or could it be C:S?) update broke Node Controller and Intersection Marking Tool mods on Linux (preventing to access a system installed mono-devel libs). That has a workaround though: https://github.com/MacSergey/NodeController30/issues/92

Unfortunately, only a few days passed and the game stopped working for me completely. It is not related to mods or anything, it just fails to load.

Now, after a week with that and tinkering around I noticed that the first run works, so that makes it even weirder. But also suggests it might not be my computer install issue? Although tried many things this past week, I am ultimately running the standard Ubuntu 24.10 with Nvidia drivers. Currently older ones - Nvidia 550, but I've also tried 560 and beta 565. Also various kernels - currently on Linux 6.12, but I was on 6.11 before. Anyway, considering the first run was a success I don't think this is related to any software stack I am having.

This is the log it gives me for the second+ run:
```
Native stacktrace:

/home/USER/snap/steam/common/.local/share/Steam/steamapps/common/Cities_Skylines/Cities_Data/Mono/x86_64/libmono.so(+0x91f55) [0x7eb3e1091f55]
/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6(+0x4251f) [0x7eb3ea22851f]
/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x12c) [0x7eb3ea27c9fc]
/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6(raise+0x15) [0x7eb3ea228475]
/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6(abort+0xd2) [0x7eb3ea20e7f2]
./Cities.x64() [0x9f864b]
/home/USER/snap/steam/common/.local/share/Steam/steamapps/common/Cities_Skylines/Cities_Data/Mono/x86_64/libmono.so(+0xd1086) [0x7eb3e10d1086]
/home/USER/snap/steam/common/.local/share/Steam/steamapps/common/Cities_Skylines/Cities_Data/Mono/x86_64/libmono.so(+0x34bfe) [0x7eb3e1034bfe]
/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6(+0x4251f) [0x7eb3ea22851f]
/home/USER/snap/steam/common/.local/share/Steam/steamapps/common/Cities_Skylines/Cities_Data/Mono/x86_64/libmono.so(+0x175d74) [0x7eb3e1175d74]
/home/USER/snap/steam/common/.local/share/Steam/steamapps/common/Cities_Skylines/Cities_Data/Mono/x86_64/libmono.so(+0x171aa2) [0x7eb3e1171aa2]
/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6(+0x94ac2) [0x7eb3ea27aac2]
/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6(+0x12684f) [0x7eb3ea30c84f]

Debug info from gdb:

Aborted (core dumped)
```

The Player.log attached is from the first run (no newer gets generated). I didn't disable mods there and also it did crash for the failed `mono-devel` access which I didn't workaround so feel free to ignore the last few crash lines. It is just to proof that first run was possible and it makes absolutely no sense to me why a second+ run would not work.

Also, feel free to ignore the fact this is stored in a snap folder. It is unrelated to Ubuntu's Snap. I've tried installing Steam through that as well as directly from the deb repositories or even the Steam website, downloading the deb file manually. The results were always the same.

Do you have any idea what could be causing this or how to debug this further please?

Thank you so much.
Best regards,
Martin

Tags​

  • Compatibility

Attachments​

View attachment Player.log

 
Last edited:
  • 1Like
Reactions:
Ah, I am sorry. I am a bit lost with the Player.log I shared. Anyway, a new try and a new log. For the first run where it was successful. And with workshop & mods disabled.
These were my launch options: `__GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 %command% --noWorkshop --disableMods`

The same launch options and the second run and the game crashes with the libmono.so error mentioned above ^.
The only thing that happened in between was the Paradox Launcher Launcher update.
 

Attachments

  • Player.log
    125,9 KB · Views: 0
  • 1Like
Reactions:
And indeed. So, when I disable network after Steam installs the game, it runs even the second+ time.
Therefore I can say that it is indeed a fault of the launcher? and it works with version 2024.10 and fails with 2024.16 :(

Do you know what was updated that could be causing this error please?

Fortunately it seems the Launcher can by bypassed to run the game directly, so as per this link [under: Linux Method (Linux)]:

one can insert in the Steam game properties and launch options something along the following instead (note this is Snap specific - the path is shorter without Snap):

`__GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 /home/USERNAME/snap/steam/common/.local/share/Steam/steamapps/common/Cities_Skylines/Cities.x64 %command%`

In any case, I hope this is helpful at least to some extent, allowing you to make a proper fix. But it also means this is actually not fully related to C:S as the game runs just fine on its own, but a Paradox Launcher itself.

Thank you very much :),
... and I hope that eventually C:S2 will also debut on Linux making it possible for me to play that as well the same way I did with passion enjoy playing CO's C:S predecessors.
 
  • 1Like
Reactions:
I appear to be having this same issue. I haven't played C:S or any Steam games in months. I played yesterday and I think there was a launcher update in the background. Today, I get the same error as you. Nothing else has changed with my computer.

So I just wanted to let you know that you aren't alone.

As per the link above I deleted ~/.paradoxlauncher and then the game will work, but it downloads the new launcher in the background, so I'll have to do that every time. The instructions note a Step 4 where you can avoid this, but part of Step 4 involves opening the Properties dialogue. When I right-click to open the menu and then click on "properties" it does not open, nothing happens.
 
Last edited:
  • 1Like
Reactions: