-
Notifications
You must be signed in to change notification settings - Fork 70
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
Portal 2 segfaults when loading any level #62
Comments
It's seems to be a problem with the runtime. Portal 2 works with the freedesktop-sdk unstable/1.8 runtime. Steam has to be rebuild, since the lib32 folder changed from /app/lib/32bit/ to /app/lib/i386-linux-gnu. The new runtime also fixed #63 & #64 and I was able to complete the single-player mode (but some Linux specific bugs occured, e.g. ValveSoftware/portal2#255 / ValveSoftware/portal2#289). |
Please re-test, runtime is now updated |
It still crashes. |
@Pixelnarium Which graphics driver are you using and does it crash when loading a level or before that? I'm asking because on my system Portal 2 now crashes before loading the menu and I think it's a different (Mesa) problem. (I actually cannot start any Steam games anymore) System: Fedora 28 with a Radeon HD7870 and Mesa.
EDITED: Don't reference unrelated issues (use code block instead of quote). |
#130 is one possible source of crashes. I'm considering disabling Mesa shader cache for now since it seems to be causing a lot of issues |
Disabling shader cache fixes the menu crash. Thanks. But the rest is the same: Only #63 is fixed, sound is still stuttering and it crashes when loading a level. |
Shader cache is for now disabled, read #130 for details. Do you get the exact original stack trace now? |
For me it is the same like in the first post... all those qhull errors and the crash in vphysics.so |
Ok. Which graphics card do you have and open or closed source drivers? |
Like I said above, I have an Intel GPU with the Mesa driver. When I want to start a new game it loads the level a little bit and then crashes. Personally I don't think that this error is related to the GPU. I have a strange feeling that the flatpak sandbox interferes with some floating point operations. |
I have this game as well and open drivers, I can try to repro |
The bugs are fixed when using Fedora 27 instead of 28. That's why I was able to play through the game. I booted the live image and Portal 2 started with the current 18.08 runtime. It also worked after updating Flatpak and its dependencies (to 0.99.3), but I didn't reboot the system (in case it's necessary for a correct update). On Arch Linux I downgraded the kernel to 4.13.4 (as used in the Fedora 27 live image) but it did not fix the problems. |
I tried to repro on my Fedora 28 Silverblue (atomic) and could not. kernel was 4.17.12-200.fc28.x86_64 with open drivers on radeonsi. |
On my system it works on Fedora 28 Silverblue, too. Both Fedora 28 versions seem to have the same packages installed (diff from rpm -qa, Silverblue has a few additional, my Fedora 28 has lots additional packages, everything else is the same). Sound problems & crashes:
Runs:
|
I think you could compare the sysctl values between these systems. Flatpak itself mentiones |
The sysctl values were mostly the same and I don't see any striking name in the sysctl-diff.txt. I reinstalled Fedora 28 (both variants) and now the game crashes in Silverblue, too. I tried Portal 2 directly after installing Silverblue, with the newest updates applied and then after downgrading to the version I tested before (version 20180818), but it made no difference. |
Did you also fully update both? Last I installed Silverblue, the tree was from April |
Yes, both variants are fully updated. But I can now reproduce the bugs: It's running on Fedora and Arch Linux when Steam is started with |
Note I always change system language from Finnish to English USA the first thing I do because I dislike the localizations so that might explain why I didn't hit that |
I can reproduce this issue as well |
It only depends on LC_NUMERIC or most likely only the decimal separator. It works when the locale uses a point (The example values are the result of Crashesbs_BA.utf8: 54548,00 Runsen_GB.utf8: 54,548.00 The backtrace looks exactly as in the initial report and I don't know what to do about libthread_db:
|
All the symbols in the trace belong to the game then. |
Investigations in #62 revealed differences in LC_NUMERIC may result in crashes. Force it to be C (generic). Downside is numbers may look non-native but that's not a very high price to pay. Can be disabled through flatpak override --env=LC_NUMERIC= com.valvesoftware.Steam
Can someone here double-check that LC_NUMERIC=C works for you that were able to repro the crash? |
It works! Great job figuring that one out. |
Update with workaround should be out around now |
Yes, just updated and now it works even without manually setting --env=LC_NUMERIC=C. |
By the way, this also fixes the stuttering audio and reverse y-axis always being on for me. |
I wonder why this happens only with the Flatpak version. Why is Steam able to handle this correctly when running without Flatpak, but not with Flatpak? |
I'm not sure but given how Steam network support breaks with unexpected /etc/localtime symlinking setups, I'm hardly surprised by anything anymore |
Added comment to https://github.com/flathub/com.valvesoftware.Steam/wiki/Frequently-asked-questions, closing |
This doesn't happen on host system.
The text was updated successfully, but these errors were encountered: