My guess is whatever made the games launch scripts no longer pick up the library paths themselves is responsible for all the issues, its just nothing obvious was upgraded.

The games log files just contain nothing at all, they arent even created so they are of no use.

Xcom 2 Launcher Not Working Update To Mesa

I thought maybe the update to Mesa 17.2 did it, but I rolled back to 17.1.8 and it had no change.

It seems to complain about missing libraries, so I look closer and its not loading the supplied libraries that come with the game (ie, libssl.so.37 and libCoreFoundation.so.476 etc).

If I specify in the launch options an LDLIBRARYPATH, I can load the base game, but not WOTC -- it literally just loads up the base game instead, weird I cannot find the syntax to load multiple directories on LDLIBRARYPATH (its not: as a delimiter, although that seems like it would be it, its not).

EDIT: So this is an AMD RX480 gpu running on all open source drivers, (hence mesa).

This line LDLIBRARYPATH.libx8664:.libx8664 command -allowconsole to the launch options makes the BASE game run, but WOTC still crashes.

Mesa 17.2 crashes WOTC right at the very beginning of the loading bar, Mesa 17.1.8 crashes at the very end of the loading bar.

Good for me EDIT: Spoke way too soon, the launcher loads, and the game begins to load but crashes shortly after the company logos play and it shows the Reaper looking at the commander in the pod.

Xcom 2 Launcher Not Working Mods To Make

SIGSEGV(11).;( I removed all mods to make sure that wasnt an issue, still remains.

I searched the forums here and there is literally nothing even remotely close to what Im describing, unless its not in Multimedia and Games.

My issue isnt garbled or bad graphics, the game doesnt launch.

The workaround salsadoom posted above works for me (so far), but only with steam-runtime, not with steam-native.

Case in point, the game I played that broke was Shadow of Mordor due to pacman -Ql icu grep libicui18n.

It should work universally with many steamgames and minimizes typing errors that easily happen with fully qualified paths (for instance: steamapps is usually lower case).

In this case there is indeed a libCoreFoundation.so.476 in.localshareSteamsteamappscommonXCOM 2libx8664 -- which the games now for a sudden demands.

At first I overlooked that, because I only searched with locate.

I did not find that library anywhere else and even google is relatively quiet about it.

But a few days ago somebody reported a similar error for a Warhammer game in this forum.

XCOM2 and probably most games just add to the library path at launch from a script, its just it stopped working for some reason.

Even if LDLIBRARYPATH did fix it, its a bit of a poor solution since it misses the underlying issue.

The crappy part is now that even though the game finds all the libraries it wants, it still crashes at the loading screen.

Thats why I initially thought It might be related to the mesa update, but I tried rolling back the mesa packages and it crashes anyway so that rules that out.

If nVidia people are having similiar issues then something weird happened.

Ive rolled back a few other packages that absolutely shouldnt cause these problems but Im desperate at this point.

Just a missing library is pretty easy to fix, this is something weird, because it crashes if it finds its libraries anyway.