Could you redirect all output from steam using the command:
steam > /dev/null 2>&1
Does the lockup still occur when launching steam this way?
I've been using Steam on Arch for months now without this ever occurring on multiple machines. I haven't yet tried CS:GO, but I've never seen games/steam directly log to journald. Could you show the output of: journalctl -b | grep steam
Lastly, it looks as though you have some ELF class mismatch issues, ensure you have all relevant 32-bit libraries. Steam is complaining excessively about 32-bit support in your log, which mine doesn't.
If I launch it using Rofi I can not redirect the output.
The output of the journalctl:
https://gist.github.com/fxdave/2ec5d001c47f10be162a36dba2bc823b
If I launch it by terminal, everything is fine.
Sidenote:
Heavy Parallel I/O tasks cause luck up. (I don't know why) May I should form an issue against linux kernel.
I finally determined what causes the deadlock: my CPU temperature above 80 °C. I may clean the cooler.
Thanks for help.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
I ran steam in terminal in order to see the output and to not write the log to the ssd.
Here the output is.
Steps for reproducing this issue:
Yes I know this is also a CSGO and also a Linux issue, but if Steam stops writing to the journald (, because why would it? Steam is not something like a system process which has importance to log.), then I could run the steam normally without terminal.