Right, bad wording, I realize it's not a bug. So is there a recommended way to update glibc, considering there is no linux-c8 port yet? I found a forum post where someone suggests copying it from centos8 and booting with newer linux newer kernel (that's available in fbsd13 current apparently). That sounds like it might break things...This is not really "fixable" (it's not a bug in the first place) unless you update all glibc libs in-place.
This is relatively safe, however you must replace all glibc libraries (ld-linux.so, libc.so, libm.so, libpthread.so and so on) simultaneously, they have internal dependencies.So is there a recommended way to update glibc, considering there is no linux-c8 port yet? I found a forum post where someone suggests copying it from centos8 and booting with newer linux newer kernel (that's available in fbsd13 current apparently). That sounds like it might break things...
No.Does/can libc6-shim help with this?
I tried a few new games that I got, both Unity, where the grey Unity logo comes up on launch, but then it exits out.
LD_PRELOAD=${LD_PRELOAD}:monofix.so %command%
Cool, thank you! Monument worksLD_PRELOAD=${LD_PRELOAD}:monofix.so %command%
"Curl error 7: Failed to connect to cdp.cloud.unity3d.com port 443: Connection refused" indicates it might benefit from pathfix.so as well. Also, the game is called Crazy Wheels.Crazy Cars gets a bit further; it passes the Unity splash screen but then freezes on the first image after that and the music starts playing. But at this point, no menu comes up and I need to kill the process to get out of it. Log looks interesting, but I'm not sure how to solve it. Let me know what you think.
Native stacktrace:
/usr/home/scratchi/.steam/steam/steamapps/common/Crazy Wheels Demo/CrazyWheelsDemo/CrazyWheelsDemo_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so(+0xd805c) [0x80d6d805c]
/usr/home/scratchi/.steam/steam/steamapps/common/Crazy Wheels Demo/CrazyWheelsDemo/CrazyWheelsDemo_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so(+0x5bdff) [0x80d65bdff]
[0x7ffffffff514]
Debug info from gdb:
mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb
Obtained 1 stack frames.
#0 0x007ffffffff514 in (Unknown)
That's fine, thanks for all the help provided to this point. Just an FYI, I'm also trying Bloody Rally Show Prologue and it fails the same way and also throws errors about libmonobdwgc-2.0.so. In this game, I even get the main menu; but then it crashes when I try to start a race. I'll poke around some more and post back if I get it working.No suggestions. I don't think I want to debug it.
That's a Windows game. How exactly are you starting it?I am trying to start Skyrim / Skyrim SE but the first results in error=234 (game directory not found) a couple of times and then finally quits with the words "missing .INI, reinstall Skyrim". The latter exhibits the same 234 errors but displays the launcher whatsoever.
Nah, monofix.so definitely doesn't work with our Proton hack. It simply won't be loaded at all.Using monofix.so the button "Play" becomes clickable (else a "no audio device" error prevents launching)
Linux or Windows Portal 2?EDIT: Portal 2 definitely does some stuff (meaning it creates a window and does not immediately crash) however the window is just a transparent outline.
Using freebsd-proton configured using the scripts from your git https://github.com/shkhln/linuxulator-steam-utilsThat's a Windows game. How exactly are you starting it?
I have tried both. Linux opens a window (as seen in the screen from my previous post) but then the game does not start. Windows (using the previously mentioned proton install) starts and immediately closes.Linux or Windows Portal 2?
If you pay attention to the console you should see that Windows version of Portal 2 exits on an assertion check in the glibc shim library we are using. This is being worked on.I have tried both. Linux opens a window (as seen in the screen from my previous post) but then the game does not start. Windows (using the previously mentioned proton install) starts and immediately closes.
I was testing Linux Portal 2 with Haswell's HD Graphics 4600 yesterday and there it hangs on startup 3 times in a row, each time requiring ctrl+c in the terminal to proceed. (Don't ask me what it is, I don't know. It's an incredibly odd issue.)Linux opens a window (as seen in the screen from my previous post) but then the game does not start.
.
.
.
src/clientdll/appdatacache.cpp (2679) : Assertion Failed: !bSharedKVSymbols
src/clientdll/appdatacache.cpp (2679) : Assertion Failed: !bSharedKVSymbols
src/clientdll/appdatacache.cpp (2679) : Assertion Failed: !bSharedKVSymbols
src/clientdll/appdatacache.cpp (2679) : Assertion Failed: !bSharedKVSymbols
src/clientdll/appdatacache.cpp (2679) : Assertion Failed: !bSharedKVSymbols
src/clientdll/appdatacache.cpp (2679) : Assertion Failed: !bSharedKVSymbols
src/clientdll/appdatacache.cpp (2679) : Assertion Failed: !bSharedKVSymbols
src/clientdll/appdatacache.cpp (2679) : Assertion Failed: !bSharedKVSymbols
src/clientdll/appdatacache.cpp (2679) : Assertion Failed: !bSharedKVSymbols
src/clientdll/appdatacache.cpp (2679) : Assertion Failed: !bSharedKVSymbols
src/clientdll/appdatacache.cpp (2679) : Assertion Failed: !bSharedKVSymbols
src/clientdll/appdatacache.cpp (2679) : Assertion Failed: !bSharedKVSymbols
Warning: failed to set thread priority: set failed for -10: -1: setpriority() failed
Warning: failed to set thread priority: set failed for -10: -1: setpriority() failed
[2021-07-07 03:57:06] Background update loop checking for update. . .
[2021-07-07 03:57:06] Checking for available updates...
[2021-07-07 03:57:06] Downloading manifest: https://cdn.akamai.steamstatic.com/client/steam_client_ubuntu12
Installing breakpad exception handler for appid(steam)/version(1623193086)
[2021-07-07 03:57:07] Download skipped: /client/steam_client_ubuntu12 version 1623193086, installed version 1623193086, existing pending version 0
[2021-07-07 03:57:07] Nothing to do
pkg upgrade
and that'll be it?In fact the 13 i386 quarterly repo was already synchronized 24+ hours ago, while amd64 still isn't despite the second build for the new quarterly branch being started already (which means those syncs are probably going to compete for the network bandwidth). This whole process is really quite broken in practice.It takes 4-5 days for the official ports to get built. Any time now.
Now synchronized.while amd64 still isn't