protonscr

steam stopped working after recent update

steamclosed Steam clientDistro Family: Arch
ValveSoftware/steam-for-linux#9665 · opened 2023-06-18 by TerryF0ld · updated 2023-06-18 · 9 comments · github
TTerryF0ld 2023-06-18 github

steam stopped working after recent update

  • Steam client version: 1686880776
  • Distribution: manjaro
  • Opted into Steam client beta?: [No]
  • Have you checked for system updates?: [Yes]
  • Steam Logs: steam-logs_tar.gz
  • GPU: AMD

Please describe your issue in as much detail as possible:

it won't start after steam

(process:2399): GLib-GObject-CRITICAL **: 13:03:08.331: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(process:2399): GLib-GObject-CRITICAL **: 13:03:08.331: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe8628db0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe8627500
GetWin32Stats: display was not open yet, good

solution to this problem, helped me: https://github.com/ValveSoftware/steam-for-linux/issues/9588

TTerryF0ld 2023-06-18 github

The steam process appears, after a while it closes, nothing else happens

Kknedl1k 2023-06-18 github

Same issue on Arch Linux here. After the recent UI update.

JJusix 2023-06-18 github

It works for me when started through bash. But startup needs about 5 minutes...

Sserhii-nakon 2023-06-18 github

I have the same problem on Debian 12, where Steam client installed from Flatpak and I also can run it using bash only.

Kkisak-valve maintainer 2023-06-18 github

Hello @Jusix, @serhii-nakon, you've described the symptoms of the issue being tracked at #9383.

Sserhii-nakon 2023-06-18 github

Hello @kisak-valve , I think no, because I don't set DRI_PRIME=1

JJusix 2023-06-18 github

I don't use any hybrid GPU solution.

TTerryF0ld 2023-06-18 github

solution to this problem, helped me: [#9588](https://github.com/ValveSoftware/steam-for-linux/issues/9588)

Kkisak-valve maintainer 2023-06-18 github

Hello @TerryF0ld, glad to hear you found a workaround. due to the abundance of cross-posting of unrelated issues, I'm going to close this in favor of the older issue report.

Hello again @Jusix, @serhii-nakon, https://github.com/ValveSoftware/steam-for-linux/issues/9383#issuecomment-1584898530 has the main detail for the common case where the desktop environment is setting DRI_PRIME in reaction to PrefersNonDefaultGPU=true in Steam's desktop shortcut. You can have an Intel GPU or AMD APU hanging out in the background, even if you don't usually use it because you (assumedly) have a discrete GPU as well.

The common comparison to troubleshoot that is to compare starting Steam from a terminal versus from the desktop shortcut. If you're seeing an issue that happens when Steam is started from a different terminal, but behaves when called from a bash terminal, please open a separate issue report focusing on that detail.

Upstream links