$ env WINEPREFIX=$HOME/.wine-test /opt/steam-utils/bin/lsu-wine-env wine64 winecfg
Segmentation fault
wine: '/usr/home/steamdev/.steam/steam/steamapps/compatdata/280790/pfx' is a 64-bit installation, it cannot be used with a 32-bit wineserver.
While I don't have this issue, I do observed that there below error in your log:
I play 64bit games with the steam native proton and 32bit with emulators/wine-proton.
Have you tried Creativerse with the steam native proton? I suppose emulators/wine-proton won't work for Creativerse as the game is 64bit.
Readme tells you to install wine-proton twice specifically to make it work in WoW64 mode. Is it broken for 64-bit games somehow?I suppose emulators/wine-proton won't work for Creativerse as the game is 64bit.
~$ cat utils
~$ sudo su steamdev
Sorry, it's just that other people say what works for them, but how? - I am using the same version of the latest version of FreeBSD. So is this a bug in the wine package? i386-wine-devel doesn't fit - I've checked.I thought we had already established this involves a Wine segfault. Why do you want me to review unrelevant steps again?
FYI, unityfix.so has been renamed to monofix.so and now contains one more workaround. The table at https://github.com/shkhln/linuxulator-steam-utils/wiki/Compatibility has been adjusted accordingly.I just dropped a yet another workaround (can't help myself, sorry) into steam-utils. This one deals with Unity games crashing on startup with a stack overflow error. Typically they print something like "Stack overflow in unmanaged: IP: 0x801911013, fault addr: 0x7ffffffe7c58". To check whether this might be applicable to your games rungrep -i "stack overflow" ~/.config/unity3d/*/*/*.log
. Then in Steam set the launch options toLD_PRELOAD=${LD_PRELOAD}:unityfix.so %command%
.
Hi Alex,Readme tells you to install wine-proton twice specifically to make it work in WoW64 mode. Is it broken for 64-bit games somehow?
I'll bite. Why are you using 'sudo su <user>'? Just use one of them.Does anyone know a way to run two CSGO games? Doesn't work on FreeBSD 13 (error: only one instance game can be run ...), but on FreeBSD 12.2 it worked fine:
?Bash:sudo su steamone -c 'steam "steam://run/730"' sudo su steamtwo -c 'steam "steam://run/730"'
sudo su - just comforteble.I'll bite. Why are you using 'sudo su <user>'? Just use one of them.
?Обнаружить Linuxulator или мои предварительно загруженные общие объекты довольно просто. Steam (VAC) уже отправляет домой эту информацию каждые 20 минут или около того.
It's not comfortable, it's just wrong, "sudo user" will do the exact same thing.sudo su - just comforteble.
It's not comfortable, it's just wrong, "sudo user" will do the exact same thing.
Because -c is a su flag, not a sudo one. The correct is sudo -u <user> <command>.Thanks, I didn't know, I need to check
OUCH!
[admin@ ~]$ sudo steam -c steam
Steam doesn't appear to be installed for user root. Perhaps you forgot to run steam-install?
[admin@ ~]$ sudo steamdev -c steam
sudo: steamdev: command not found
[admin@ ~]$ sudo su steamdev -c steam - WORK
OkBecause -c is a su flag, not a sudo one. The correct is sudo -u <user> <command>.
It seems you're blindly copy/paste stuff from internet to make it work, I would suggest learn sudo and su, the man isn't too extensive and will keep you from make mistakes in the future.
./SteelRats-Linux-Shipping: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by ./SteelRats-Linux-Shipping)