Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

steam stopped working after recent update #9665

Closed
TerryF0ld opened this issue Jun 18, 2023 · 9 comments
Closed

steam stopped working after recent update #9665

TerryF0ld opened this issue Jun 18, 2023 · 9 comments

Comments

@TerryF0ld
Copy link

TerryF0ld commented Jun 18, 2023

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: #9588

@TerryF0ld
Copy link
Author

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

@knedl1k
Copy link

knedl1k commented Jun 18, 2023

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

@Jusix
Copy link

Jusix commented Jun 18, 2023

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

@serhii-nakon
Copy link

serhii-nakon commented Jun 18, 2023

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

@kisak-valve
Copy link
Member

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

@serhii-nakon
Copy link

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

@Jusix
Copy link

Jusix commented Jun 18, 2023

I don't use any hybrid GPU solution.

@TerryF0ld
Copy link
Author

TerryF0ld commented Jun 18, 2023

solution to this problem, helped me: #9588

@kisak-valve
Copy link
Member

kisak-valve commented Jun 18, 2023

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, #9383 (comment) 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants