Hello @Gepp35, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
Bloob Bowl 2 writes gigabytes of log spam to ~/.xsession-errors
Issue transferred from https://github.com/ValveSoftware/Proton/issues/2457.
@jwakely posted on 2019-03-25T20:30:45:
After starting the game and then quitting as soon as the main menu appeared, the steam-236690.log file was 246MB and so github won't allow me to upload it!
This is a log file created by interrupting the game as soon as the first "Viewport hasn't been setted" errors were written to the log:
The game writes the line "Viewport hasn't been setted" to the file ~/.xsession-errors thousands of times per minute. Over the space of a few days it logged that line 3.8 billion times, and filled my home partition (which previously had 100gb free).
In a terminal run tail -f ~/.xsession-errors | grep setted and then start the game. Watch the logs fly by ...
I forgot to mention in my report that the game actually runs really well for me, and I didn't even realise there was anything wrong until my home partition filled up for the second time in a week. After that I went looking for the problem and found that Blood Bowl 2 was doing all this logging. The steam-236690.log file shows loads of exceptions being raised, but this doesn't affect game play at all.
As a workaround, I have to rm ~/.xsession-errors and reboot before the file fills my disk again.
The simplest workaround is to Exit t he Steam client and restart it from a terminal window, redirecting the output to /dev/null:
steam >/dev/null
That way nothing gets written to .xsession-errors
Interesting. The game continually dumps that via OutputDebugString, so that's why your Steam log grows so fast. I have no idea how that message makes it into .xsession-errors, though... that doesn't happen on my Arch Linux machine.
Edit: Ah, it gets dumped to stdout. Probably whatever launches Steam is logging its output to .xsession-errors.
It's the Xorg server that writes it there, because that's what the file is for: capturing the output of X Windows processes.
If I launch steam from an xterm then the output goes to that terminal, but that's not how I launch the steam client (and neither do most people, I assume).
Interesting. We could redirect stdout to /dev/null by default. It's been brought up before (Steam also logs games' stdout to /tmp/dumps/, which will grow just like your xsession file).
Could that redirecting be done on a game-by-game basis, e.g. via the launch options, so that output is only discarded for games known to spew too much?
Hello @jwakely, it may be worth trying > /dev/null (or > /dev/null 2>&1 to include stderr) in the game's launch options. This always has to be the last thing in the launch options.
@kisak-valve yeah that works, thanks. That's a perfectly good solution as far as I'm concerned, I can play BB2 without needing to run steam from a terminal and without worrying about disks filling up. Everything else works well.
Oh, except after switching away from the game with Alt-Tab and then back again, you need to press Alt once to re-enable the keyboard. I've seen a few comments saying that for different games on protondb.com. It's not a big deal, you just have to remember to press Alt again.
proton 3.16-4x1 2018-11PROTON_LOG=1x1 2018-11
Compatibility Report
System Information
I confirm:
Symptoms
Game doesn't launch with steam proton. It launches using Lutris until before the game menu. Seems to work with Nvidia video card.
Reproduction