Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal. You can also buy games using our partner links for GOG and Humble Store.
Pillars of Eternity (one not two)
Page: «2/2
  Go to:
whizse Sep 8, 2018
At least on my system it's a 64bit binary, so I would be surprised if installing 32bit libs would do much ^_^

[Inferior 1 (process 12270) exited normally] it doesn't seem to be crashing at least, it just exits without any reason?

Did you check the Unity log as suggested by others previously in the thread?
_J_30000 Sep 8, 2018
Apologies for the delay in coming back...
* I checked .config/unity3d/ there is no Obsidian... or Pillars... folders at all
* I did find that the Player.log updates everytime I try to start Pillars and says
[code]Player is already running
(Filename: Line: 439)/code]

A quick google indicated that could be related to having a chrome window open or chrome process but even rebooting and manually ensuring all chrome processes are killed still produces this bug - I am wondering if this is an old unity version that "thinks Gnome is running a unity process" or something ?

now downgraded nvidia driver to version 390.87 and it works -- so < the version of unity3d shipped with > PoE does not work with 396.54 ... ok lets see if once up and running I can get it to restart after driver update (doubt it) thanks for all the help
whizse Sep 8, 2018
It looks like Unity is quite broken when it comes to making sure only a single instance of the game is running. There's some analysis here:
https://forums.obsidian.net/topic/84736-game-dosent-start-using-the-steam-client-linux/
https://steamcommunity.com/app/240760/discussions/1/617320628324498086/

The bug was fixed, but each game affected needs to be updated. I'm not sure what version of Unity PoE uses.
https://forum.unity.com/threads/bug-in-unity-when-running-chrome-on-linux.441253/

I guess not only Chrome but any program that uses the same way to spawn child processes will trigger the bug.
whizse Sep 8, 2018
TLDR, at some point Unity ends up comparing the command lines for running prcesses with the string "/proc/self/exe" and not what readlink("/proc/self/exe"... points to. The lesson here is for parents not to name their children /proc/self/exe. Looking at you Chrome!

Here's very quick python script to find any process on the system that might be a problem:
import os

procdir = "/proc"
for proc in os.listdir(procdir):
    try:
        with open(os.path.join(procdir, proc, "cmdline"), "rt") as fd:
            cmdline = fd.read()
            if "/proc/self/exe" in cmdline:
                print(proc, cmdline)
    except Exception:
        pass

(Considering Skitt's Law and that I'm criticizing Unity here, the code above probably will not work!)
_J_30000 Sep 11, 2018
Finally figured it out!

It was the VPN connector application (PIA) that was causing Unity to think that it was already running...

also works with nvidia 396.54 again

very odd but perhaps for future reference...
damarrin Sep 11, 2018
Might be worth letting them know, I guess?

Also, PIA has OpenVPN profiles, which should work through straight-up Network Manager without any additional software (once you get openvpn installed, as it's possibly not).
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register


Or login with...
Sign in with Steam Sign in with Google
Social logins require cookies to stay logged in.