Steam Hangs on Startup #9658
Comments
|
Same issue here, except with Gnome 44.1 running on Wayland. It does appear that the core issue is spawning the Steam window as all of the background processes continue to work. For example, clicking on anything on the system widget does show in the logs, along with other usual messages. The Otherwise, nothing really obvious shows up. Tested with the stable release and the latest beta (June 17th re-release) and with the latest Nvidia drivers (535) and the version previous (530). The same tests all under X11 work fine in all combinations. This is all on a Ubuntu 23.04 system. |
|
steam with -bigpicture seems to work for me even when normal one is broken. |
|
Launching steam with -vgui runs with old UI. But the friends tab seems to be broken and shows as disconnected even though it isn't. |
|
Thank you, running with -vgui fixed it for me, since I don't have any friends. I use Ubuntu with an rx7900xtx and other good specs. I don't know how to get the steam logs, but I'll link the text file from when I ran it in the command line. |
|
Running with -vgui works to start Steam, however, Dota 2 graphical performance is impacted drastically. For some reason FPS drops from ~150 down to less than 10 and it is unplayable. Very odd! I notice in other issues removing This also persists with today's beta client patch applied. |
|
For me, -vgui just had Steam hang on logging me in, although that was
probably just a weird networking fluke. Steam has no trouble logging me in
on the new UI.
…On Tue, Jun 20, 2023, 02:40 Edward Savage ***@***.***> wrote:
Running with -vgui works to start Steam, however, Dota 2 graphical
performance is impacted drastically. For some reason FPS drops from ~150
down to less than 10 and it is unplayable. Very odd!
I notice in other issues removing xdg-desktop-portal-gnome is a common
suggestion so just making a mention here that it has no effect.
This also persists with today's beta client patch applied.
—
Reply to this email directly, view it on GitHub
<#9658 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANHFQFTEEGQGBJXWKW6P6HLXMFOYHANCNFSM6AAAAAAZKTMRUM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I was getting the same error, with |
|
I can confirm this issue is happening on archlinux. |
|
Seems to be related to #9634. I was on driver 535.54.03-1 and I saw the same |
|
No opcode errors in dmesg in my case nor does downgrading the driver help. Retested with all the fixes in the last two days betas, no dice, even after |
|
I'm getting the same after picking up the latest package from the Manjaro repositories. Full details follow: I've been trying to get Steam running on my new Manjaro Cinnamon build with very mixed results. I managed to get it running once and tested some games then on reboot the Steam Client would not load, either in (Native) or (Runtime) variants. I tried uninstalling and re-installing the steam packages to no avail. After looking for help online I first did I then ran it again and this time it loaded up, so I installed a few games again and tested them through. Performance was lacklustre, so I tweaked the CPU power performance and rebooted. 1 game was looking better but another was still not great so I tried switching a proton version and it crashed, so I went for a reboot. On reboot, once more the Steam client would not start. I ran When I run steam my output looks like this (on Here's my INXI... I have just done a full uninstall of the Steam packages (steam linux-steam-integration steam-native-runtime), renamed my steam directroies again (as noted above), then a reboot and then ran On clicking the icon on the desktop various dialogs appeared, updating and installing parts of the Steam client and then everything went quiet again. Attempting to run from the command line is providing the same output as above. Not sure where to go from here - It feels like the package is broken. This article on the Arch Wiki is potentially similar: https://bbs.archlinux.org/viewtopic.php?id=286683 I've now tried all the parameter overrides posted here - none of them worked for me. The only thing I haven't tried is removing |
|
I found a workaround for this on my Manjaro Cinnamon install but it's ... weird. The full details can be found on the Manjaro forum discussion here: https://forum.manjaro.org/t/problems-getting-steam-running/143276/19 THE (WEIRD) SOLUTION I’ve tried disabling all the Startup applications (except Steam) and that made no difference at all. I have run some tests to see whether it’s actually the closing of docker desktop that’s helping or that it was started - I wondered whether DD is waking up something that Steam needs to run which it’s failing to kick itself. This theory holds true. It’s not closing Docker Desktop that gets Steam working, it’s actually running it. I wonder if it’s not actually docker desktop that’s helping directly but a dependency that it kicks off. I wonder whether steam needs to use this or tries to kick it but it won’t respond? (I am purely guessing at this point) - The comments on the Arch Wiki in regard to flatpak may have a common source. I’ve now set my Startup applications so that Docker Desktop starts after 15 seconds, with Steam starting at 2 (expecting it to fail that early on) - This seems to kick them both into touch and then, as long as you give it a minute or so, you can then reliable and rapidly start Steam! It’s an odd workaround but I’ll report back over the next few days on it’s efficacy. |
|
About this error: seems that can be solved this way: |
|
I spent some more time playing with this today to look into the Docker Desktop report above. While I couldn't replicate that result I did find that the main Steam window will partially spawn, very infrequently, if the frozen login screen is killed. In the second picture below you can see a menu with "Home", "Collections", and "Downloads". The other menus work, and if I guess where buttons are I can start games or open Chat, and move the window such that the menus open elsewhere.
If it's any help I grabbed And for anyone else looking at
|
|
All games started via the invisible library window cause buggy client warnings. Playing around with the ghost window can trigger a crash with this Mesa fault. Steam Diagnostics (Runtime Information) Lots of unexpected initialisation failures with renderers like this one. Wayland might not have direct rendering but I'm imaging the Steam XWindow should have it. The libraries it says aren't available are on disk and I couldn't spot any stale copies from the named errors hanging around. Hopefully this points to something actually useful for debugging @kisak-valve. 🤞 |
|
Yup, looks like a few of these Wayland tickets are all the same fallback case. Though I'm a little confused why the rendering worked fine for months in the beta channel and only broke when the big UI refresh release went to the stable channel. All I did was update Steam on the day the patch came out and suddenly I couldn't use it on Wayland. I'll step through the library imports tomorrow and see what file is broken or in the wrong place. |
Exactly why I'm so weirded out by this bug since there was no indication of this prior. |
|
Fixing GLX acceleration fixed Steam and games running within it. Thanks a bunch Kisak. 🚀 |
|
I managed to get it to work by uninstalling steam, and then reinstalling without native-runtime. Assuming some libraries are conflicting, i didn't spend much time verifying the library. I double checked and broke it again by installing the native-runtime and the normal runtime stopped working again. |
|
I didn't even have native-runtime installed before. Installing it and running Steam through that seems to have fixed my issue though, weirdly enough. |
|
looks like -vgui is removed now even though issue is unresolved. very cool |
|
looks like new steam ui has problems with my xorg configuration. this (reduced) config uses igpu and dedicated gpu to run one screen each (i3 as wm) When I remove the igpu driven screen steam runs just fine. It also works when i run it under gamescope unmodified which is what made me think of my xorg config in the first place. |
altough because But now XWayland is Xorg ripped off and a lot of from Xorg is missing because Red Hat try to clean it for todays old issues. So if Steam has problems it is maybe because Chromium and Steam stack upon that is not prepared well for Wayland and also WebGPU and a lot of programming is behind the curtain in Google for Chrome and Steam waits. So maybe some xorg config do it, but reporting bugs and find what config do it is only part of equation for better XWayland and maybe game recompilation because new framework updates for games(like SDL) could bring native Wayland. |
Your system information
Please describe your issue in as much detail as possible:
When I start my laptop, as usual, Steam starts up automatically. This time, it has the fancy new loading screen that I assume comes with the new UI update. But Steam never opens up into my library: the circle just perpetually spins. The Steam icon does appear in my system tray, but I can't open any recently-played games through it and trying to get to anything within the Steam runtime just results in a similar hang. Exiting Steam from the tray works, so when I do that and start Steam again, it checks for updates and seems to successfully log me into my account, but it freezes when trying to load whatever interface it's trying to load (I assume the store, but the hang happens when I try to open my library as well).
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: