BTW: Is this a real workaround to install some kind of other steam version (snap-version)? I actually have now idea what that is and how to do this :(

I can confirm that this guide works: https://www.gloriouseggroll.tv/having-steam-game-problems-on-your-distro-try-the-snap-pak-of-steam/
You can skip over the account creation and disk mounting parts.

All you need to run is:

pacaur -S snapd-git
sudo systemctl enable --now snapd.socket
sudo systemctl start snapd.refresh.timer
That installs the snap package from the AUR git repo.

sudo snap remove solus-runtime-gaming linux-steam-integration
sudo snap install --edge solus-runtime-gaming
sudo snap install --devmode --edge linux-steam-integration
That installs the Solus Steam runtime snaps.

snap run linux-steam-integration
That runs the newly installed snap version of Steam.

You can now install the game and play it after you set the compatibility workaround for the game under game properties -> set launch options.

MESA_GL_VERSION_OVERRIDE=4.5 MESA_GLSL_VERSION_OVERRIDE=450 %command%

That's great about snapd but i cannot test that method because i am trying to run the game from a shared library in steam.Shared libraries do not seem to work with snap steam.

a little update: after too much ****ing around with my system and after some distrohopping for testing i have now decided to setup a fresh install of gentoo.

The interesting part is that i am now again unable to start Dying Light (not related to lspci of course)

{20:54:20.884} INFO: [INFO] > Caught signal 2 (Interrupt).
{20:54:20.887} INFO: [INFO] > /lib64/libc.so.6(+0x34ff0) [0x7f4b240dcff0]
{20:54:20.887} INFO: [INFO] | /lib64/libc.so.6(__select+0x33) [0x7f4b24197fe3]
{20:54:20.887} INFO: [INFO] | libropengl.so(_Z25InitGpuDeviceAndVendorIDsv+0xe4) [0x7f4af0b34df4]
{20:54:20.887} INFO: [INFO] | libropengl.so(_ZN12SRendererAPI11RInitializeEPv+0x73f) [0x7f4af0b35adf]

the system is compiled with the same optimizations as before but i'm still on stock gcc (6.4) while on my old installation i updated to 7.2 and recompiled the whole system with it.

as i still have a working disk image of my old installation i should be able to find out what step exactly is needed for my system to be able to run Dying Light (but no promise it will work for other distributions)


as always i'm a bit short on time, so updates will follow infrequently

I tried the lspci soft link. I get a white line that creeps from left to
right, presumably a loading bar. The screen goes black and then nothing.
Ubuntu works.

The game runs pretty well in wine 3.1-1 under antergos.

The game runs pretty well in wine 3.1-1 under antergos.

Were you just curious, or would you seriously rather play the Windows version on Wine than play the game with the Solus snap packages or on a supported distro? :)

Was just curious. But it's great progress. It's playable on an rx580 and a ryzen 7 at high settings.

After all the wine staging patches get merged, it should work even better.

After finally being able to play the game on Arch with the help of Snap and this little tutorial. https://www.gloriouseggroll.tv/having-steam-game-problems-on-your-distro-try-the-snap-pak-of-steam/

It ran relatively stable, some graphical glitches, some crashes, but it was playable.

When it stopped working I thought the newest snap git version from the AUR was one step too much so I downgraded to the one it definitely ran quite well on. It still crashes with a core dump, even after disabling the steam overlay, which it doesn't like, as many games don't.

Where should I post bug reports? With the snap developers, the solus developers. I guess I don't have to bother the DL devs...

It works for me now, in Cross Linux from Scratch. The lspci symlink did the trick.
Since my last post I recompilied Mesa and I believe cleared my shader cache.

I get a bad stutter with the frame rate which makes it unenjoyable.

Didn't try with wine yet and have honestly very little time on my hands right now. All I can say is that something did change between 13- and 17- profiles in gentoo that seem to break dying light again for me. Gotta ask egon2003 if he has already recompiled his gentoo world with new profile as well and if it's still working for him. Also interesting that newer version of the snap seem to break DL as well. Might be interesting to check what commits happened regarding gcc and glibc.

I get a bad stutter with the frame rate which makes it unenjoyable.

https://steamcommunity.com/app/239140/discussions/0/604941528477881594/
I tried that and it works.
You can also enable vsync in the config file manually without having the game crash while trying to do it in the options menu.

I am now trying to use exodus to get it running on antergos via the Linux Mint 18.3 packages.

I've managed to pinpoint the problem to the "libc.so.6" library. I've pre-loaded the one from Linux Mint 18.3 and now I get the error

gdb: ./dependencies/libc.so.6: version `GLIBC_2.25' not found (required by dependencies/libpython3.6m.so.1.0)

when debugging with gdb.

Can anyone upload somewhere the 64 bit "libpython3.6m.so.1.0" file from Linux Mint 18.3 so I don't have to reinstall it just for one file? :)

I've managed to pinpoint the problem to the "libc.so.6" library. I've pre-loaded the one from Linux Mint 18.3 and now I get the error

gdb: ./dependencies/libc.so.6: version `GLIBC_2.25' not found (required by dependencies/libpython3.6m.so.1.0)

when debugging with gdb.

Can anyone upload somewhere the 64 bit "libpython3.6m.so.1.0" file from Linux Mint 18.3 so I don't have to reinstall it just for one file? :)

libpython3.6 isn't available on Mint 18.3 / Ubuntu 16.04, but you can download the 64-bit libpython3.5 deb package here and extract the .so from the data.tar.xz if that helps. You can browse all the repository servers right in your browser, no need to install the distro.

libpython3.6 isn't available on Mint 18.3 / Ubuntu 16.04

I thought as much.
My guess is that the game requires another file, found it in the antergos lib folders, but it was a newer version that requires python 3.6 instead of 3.5.
I'll see if I can figure out who the culprit is.
The point is that the game runs on antergos & Arch via the Solus runtime. Pre-loading the libraries via a sh script does the same thing. You just need a full list of all required dependencies and their dependencies, and so on. And that's the hard part.

After installing Solus and on it Steam as well as Steam via Snap it still doesn't work.

ERROR: ld.so: object '/home/gamer/snap/linux-steam-integration/common/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
GameAction [AppID 239140, ActionID 4] : LaunchApp changed task to Completed with ""
/home/gamer/snap/linux-steam-integration/common/.local/share/Steam/steamapps/common/Dying Light/DyingLightGame: /usr/lib/libcurl-gnutls.so.4: no version information available (required by libengine.so)

As it doesn't run on Arch with my RX480 as well as on Solus I guess it is not a problem of Snap, but maybe of mesa or the compiler suites? I've found that the snap package prefers OpenGL4.4 as can be seen here https://pastebin.com/jYzQmPeR on my Solus install and here https://pastebin.com/EZjSnkL3 on my Arch install with different errors and dumps.

Anyone got it running on a RX480/RX580? If yes, on which distro, version of mesa or with what special settings?

Just testing it on Ubuntu 17.10 - no issue, game launch fine.
Tested also on OpenMandriva LX3.03 - no issue. Same on Mageia 6. Using mesa 17.3.

Ok nice to know and thanks for testing.
So far it's working on Debian, Ubuntu, openmandriva, maegia, Solus, mint and gentoo.

Guess we'll rather make a list of not working distributions?

just some info, I went to test it again today on arch via snap. I updated snapd-git from the aur, launched the game, and it ran but then froze.

I then changed the overrides from
MESA_GL_VERSION_OVERRIDE=4.4 MESA_GLSL_VERSION_OVERRIDE=440 %command%
to
MESA_GL_VERSION_OVERRIDE=4.5 MESA_GLSL_VERSION_OVERRIDE=450 %command%

game's running so far without a hitch. I wonder if the override needs to match mesa's core profile.

I'm currently on mesa 18 rc4 with a vega 64.

glxinfo:

[gloriouseggroll@shittywok ~]$ glxinfo | grep "OpenGL"
OpenGL vendor string: X.Org
OpenGL renderer string: Radeon RX Vega (VEGA10 / DRM 3.23.0 / 4.16.0-rc2-g91ab883eb213, LLVM 5.0.1)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.0-rc4 (git-719f2c9340)
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.0-rc4 (git-719f2c9340)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.0.0-rc4 (git-719f2c9340)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:

Ok nice to know and thanks for testing.
So far it's working on Debian, Ubuntu, openmandriva, maegia, Solus, mint and gentoo.

Guess we'll rather make a list of not working distributions?

Do you have a Nvidia card? The problem seems to persist in Solus (native/snap) as well as on Arch (runtime/snap) with a RX480.
The only distro I could get in running on was Ubuntu 17.10. Not an ideal choice as the 18.04 LTS version wants to spy on you during the install process.

The only distro I could get in running on was Ubuntu 17.10. Not an ideal choice as the 18.04 LTS version wants to spy on you during the install process.

Opt-in if you upgrade from 17.10 or 16.04...

”Upgrading users would need to purposely “opt-in” to this behaviour, as that wasn’t
explicitly asked in the past.

Dustin Kirkland