this post was submitted on 11 Sep 2023
9 points (84.6% liked)
Linux Gaming
15275 readers
153 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME
away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't think that's a solution, unless one of these installs out of the box some other version of a driver or module. And all three are rather using older versions. Maybe Mint could be a little bit more up to date.
I would propose: execute steam with PRESSURE_VESSEL_SHELL=instead (
PRESSURE_VESSEL_SHELL=instead steam
in a terminal or launcher where you type what to execute) and once you have xterm run the game with"$@" > $HOME/tmp/sniper.log 2>&1
. That will redirect the output from the process to the file which you can use after reboot to search what is the problem you are having. If there's not much inside, retry withexport WINEDEBUG=+all; "$@" > > $HOME/tmp/sniper.log 2>&1
. The latter will run very, very slowly but should print debug of everything that happens in proton