Steam is stuck in infinite loading screen after login
The same problem on Ubuntu 23.04 in a Docker container with RTX4090 + Nvidia 535 series driver
At the moment I can only run Steam with my internet completely disconnected
Same problem. I have Kubuntu 22.04. GPU - 1050TI Nothing works
@CO-Lukas Have you solved it 1 year ago?
Same issue. my pc specs is Pop!_OS 22.04 LTS 64-bit with NVIDIA RTX 4050. Gnome 42.9, windowing system x11, steam 11.01 2024, kernel 6.6.6
Same issue. Ubuntu 20.04.6 LTS 64-bit with GeForce GT 710 and Intel® Core™ i5-8400
Same issue. Trying to launch steam with internet connection leads to an indefinite loading screen. Launching without internet connection and then trying to connect yields no results sadly.
Kernel: 6.7.9-arch1-1
Downloaded steam from Pacman package (also tried the steam-native-runtime AUR package on yay, didn't work either)
Someone recommended trying BigPicture mode, didn't work for me either. It logged in successfully (The account pfp and username does display properly) but still would take me back to a login screen.
On ArchLinux forum people suggested to try a VPN but i haven't yet, perhaps this could be useful to someone: https://bbs.archlinux.org/viewtopic.php?id=291127
People also suggested it's a regional block and only appears to occur with people from uhh "problematic" countries, like Russia (exactly where i am from).
EDIT: Just tested with the most basic wireguard setup ever, steam has launched no problems. Not sure how i feel about that. After disabling the VPN it all started to work without it! What the hell, Valve?
TL;DR - Launch with a wireguard with any VPN server (as long as it isn't in your country) and launch steam, after it logs in and pages load - exit steam and then disable the wireguard. It will work then.
How that works? Why that works? Beats me; at least steam didn't rm -rf / my machine, i guess it's a plus.
EDIT 2: Well, turns out you're better off making your own steam launching script that turns on vpn for like 10 seconds and then turns it off automatically, if you manually launch steam with vpn enabled you can then disable it and relaunching steam seemed to work, an hour later i tried re-launching steam and... still the same problem. I guess the solution "Just login with vpn once and then it'll be okay without a vpn" is only temporary.
EDIT 3: The issue appears to be closely connected to a firewall setup. I've disabled mine and steam launched just perfectly! Although I have no idea how to make steam behave with a firewall on, here are some links me and my pals stumbled upon: https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711
The ArchWiki states to configure port forwarding, I'm not really knowledgeable in the connection/firewall stuff so here's the link to the wiki: https://wiki.archlinux.org/title/Steam/Troubleshooting (the tip about forwarding is at the very top)
TL;DR2 - Try disabling firewall entirely to see if the issue is gone; that helped in my case, not sure if it'll help you though. If the issue is gone after disabling firewall - welp, you gotta somehow forward or allow ports for steam.
this issue happens to me only when i launch steam from my home wifi, im from russia too. my internet provider is domru, and if i launch while my pc is connected to my phone, where the provider is megafon, it launches without issues
Hello @zmeyka3310, #10297 is more relevant to you than this issue report.
I just started having the same problem as well, and was also able to launch Steam successfully with steam -tcp.
The terminal output from running steam is a bit obtuse but it seems like something is crashing when launched with no arguments? I didn't change anything on my system, it was working one minute and stuck loading forever after a reboot.
This also happened to me today. Was working half an hour ago, then I did some seemingly-innocuous gnome update, and then I could not launch steam without adding the tcp
Possibly the gnome update is a red-herring, but its the only thing that I changed in that short window of time.
Had this same problem years ago, back then adding -tcp helped as well.
Same here. Using -tcp at launch finally worked.
Possibly the gnome update is a red-herring, but its the only thing that I changed in that short window of time.
I didn't update since my last Steam launch and I was affected today too. -tcp was also a solution for me.
I'm experiencing the same on Gentoo with the Flatpak version of Steam. It worked previously, then without rebooting or updating anything it started looping on "logging in...". It was briefly fixed by running it with `flatpak run com.valvesoftware.Steam -tcp", but now it's stuck again even with the -tcp flag, so I suspect that the issue is server-side.
It just started working again without the -tcp flag out of the blue.I'm on
arch with cachyos v3 packages. WTF
On Thu, Aug 29, 2024 at 10:33 AM Bence Göblyös @.***>
wrote:
I'm experiencing the same on Gentoo with the Flatpak version of Steam. It
worked previously, then without rebooting or updating anything it started
looping on "logging in...". It was briefly fixed by running it with
`flatpak run com.valvesoftware.Steam -tcp", but now it's stuck again even
with the -tcp flag, so I suspect that the issue is server-side.—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/8859#issuecomment-2318311007,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHTDTU2325V56IC3S3IDHLLZT5ENVAVCNFSM6AAAAAARJ3VGD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJYGMYTCMBQG4
.
You are receiving this because you commented.Message ID:
@.***>
Same here, had trouble using my Steam Deck since I couldn't log in, but figured it was something on their end. Tried it later and it worked like normal
Your system information
Please describe your issue in as much detail as possible:
What did happen:
The Steam client is stuck in an infinite loading screen after entering the login information.
What I expected to happen:
The Steam client opens and lets me launch games after logging in.
Things that we have tried to far that did not fix the issue:
Logging in on steampowered.com from a browser does not work either when using the same machine and causes the same issue. The issue does not happen when using a windows computer on the same network.
Terminal log: Link
Graphics card used: GeForce GTX 970
Steps for reproducing this issue: