New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unity3D games do not run if started through steam - but run solo #3888
Comments
Hi, A couple questions: |
here the full log. I tried googling the errors of course - what always lead back to the arch wiki, which did not help |
exact specs from the intel system - all 3 machines run same software stack (openSUSE Tumbleweed, kernel 4.0...) except the graphics driver (radeonSI and intel) ` Netzwerkinformationen: Betriebssystem: Grafikkarte: Soundkarte: Speicher: Weitere Daten: Installierte Software: Neueste Fehlerberichte: |
I gave detailed logs and would like to provide more - please someone: reply! |
I installed an OpenSUSE Tumbleweed VM and was able to reproduce the issue.
Then FMOD selects ALSA, and the crash occurs in libasound2, apparently because of incompatibility between the library in steam-runtime and the host driver. Either of the following worked around the issue for me:
|
THX! |
I've submitted an update to the openSUSE Steam package ( https://build.opensuse.org/request/show/313151 ) . It will be available in one of the next TW updates |
if alsa-devel fixes anything that means some program is linked incorrectly or dlopens the wrong library. Noone must open libasound.so at runtime. At runtime programs must use libasound.so.2. Please report that to the vendor of the program that tries to open libasound.so. |
FMOD is in fact loading libasound.so.2 , but the presence of the alsa-devel packages changes how this gets resolved, apparently. I imagine one could achieve a similar effect by using LD_PRELOAD tomfoolery. |
maybe it prefers libasound.so and then coincidentally loads the system libasound. I guess the real fix would be to remove other copies of libasound.so.2 |
As lnussel says, FMOD must dlopen libasound.so.2 rather than libasound.so, because there is no guarantee whatsoever that libasound.so is always version 2 (it could be v3 in future). Second, as a workaround, steam could provide a libasound.so symlink in the same directory its own copy of libasound.so.2 is located. |
What I do not understand yet - why did the games work (sound also) when I launched them without steam by clicking on the binary in dolphin? Is FMOD only used in steam? Isn´t the bug finaly something in the steam-runtime, which is not involved, when I run the game without steam? |
When launching outside of steam, there was no mismatch with the system libraries and the steam libraries (because the steam libraries weren't in the loader path), so either:
|
So...if I got this right... |
FMOD already opens libasound.so.2. The problem is that this resolves to the incompatible libasound2 in steam-runtime by default. |
So, what would be the real fix? |
Hello @tomtomme, are you still experiencing this issue on an up to date system? |
No, thanks
|
Thanks for the feedback, closing. |
Interesting Problem since some weeks:
For example the game "Sentinel" works fine, if I navigate to its folder and click the binary.
However if I start it with a double-click from within Steam I only see the configuration-dialogue and after hitting OK a black fullscreen-window appears and disappears instantly.
I have this behaviour for all games using unity3D engine on 3 openSUSE Tumbleweed machines:
Games not using unity3D run fine; some weeks ago also the unity3D ones worked fine.
Could this be a mesa / steamoverlay problem?
What I have tried (to no avail)
What I did not (yet) try
libudev.so.0 => not found
This rpm is currently not building for tumbleweed (Error 404):
http://download.opensuse.org/factory...4.1.x86_64.rpm
Other people seeing this?
The text was updated successfully, but these errors were encountered: