ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.13k stars 174 forks source link

Steam refuses to open after a system hang #10832

Open macccorehenni opened 3 weeks ago

macccorehenni commented 3 weeks ago

Your system information

Please describe your issue in as much detail as possible:

Steps for reproducing this issue:

  1. Attempt to run the Steam Launcher after rebooting hung system

Output of steam: steam.sh[7112]: Running Steam on debian 12 64-bit steam.sh[7112]: STEAM_RUNTIME is enabled automatically setup.sh[7227]: Steam runtime environment up-to-date! steam.sh[7112]: Steam client's requirements are satisfied tid(7290) burning pthread_key_t == 0 so we never use it

Further information

It seems to be a similar issue to issue #9744, if not a regression therein. As far as I know, no updates were pushed during the recovery. Another issue that seems relevant to the issue I am having is issue #9119. It's useful to note that both these issues have been closed, one being chalked to downstream libraries not being up-to-date, the other being an intermittent problem. I think that investigating the issues in #9119 a bit further may help, or it may not. I tried removing and reinstalling it, to get this dependency conflict from APT:

This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  steam-devices

[Package steam-launcher is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  steam-devices]

E: Package 'steam' has no installation candidate
E: Package 'steam-launcher' has no installation candidate

This was solved by reinstalling from the DEB archive, to no avail.

The version of libc installed matches that described in #9744.

macccorehenni commented 3 weeks ago

I also want to point out that this issue was NOT present in openSUSE Tumbleweed.

kisak-valve commented 3 weeks ago

Hello @macccorehenni, skimming through your pack of logs, steamwebhelper.log seems to be giving a fairly strong hint that your video driver / GPU state is not healthy:

[0428/053528.837676:ERROR:gpu_process_host.cc(985)] GPU process launch failed: error_code=1002
[0428/053528.837697:WARNING:gpu_process_host.cc(1338)] The GPU process has crashed 9 time(s)
[0428/053528.837713:FATAL:gpu_data_manager_impl_private.cc(440)] GPU process isn't usable. Goodbye.

I'd test how Steam behaves after completely closing it, then running Steam from a terminal with steam -cef-disable-gpu. It's possible that some hardware state got carried over from your system issue earlier and the video driver doesn't know how to clear the quirk state. If that's true, a cold reboot of the system might clear the quirk.