Steam: Partially Fails to Connect to Internet after Waking
This appears to be related to issue, #472 , as well. Although I think they may still qualify as separate issues, considering that one is in regards to Steams initial startup on boot, and the other is in regards to Steam reconnecting to the internet while already running after "waking" the computer.
I can confirm. After waking up PC from sleep steam becomes unusable, stuck when launching games.
until steam is restarted
Similar problem for me on OS X 10.8.3. I think in about 80% of the times the computer is waking up from standby Steam thinks that there's no connection.
Playing games works, but I can't chat or see who's online. Steam will never automatically reconnect, though. Only quitting and restarting it will help.
There seem to be entries in service_log.txt related to this problem:
Sat Jun 08 18:10:10 2013 UTC : Failed to connect to Steam Service (60)
Sat Jun 08 18:18:27 2013 UTC : Failed to create Service pipe (60)
Sat Jun 08 18:18:27 2013 UTC : Failed to connect to Steam Service (60)
Sat Jun 08 18:26:51 2013 UTC : Failed to create Service pipe (60)
Sat Jun 08 18:26:51 2013 UTC : Failed to connect to Steam Service (60)
Sun Jun 09 10:42:36 2013 UTC : Failed to create Service pipe (60)
Sun Jun 09 10:42:36 2013 UTC : Failed to connect to Steam Service (60)
I get this sometimes after a suspend wakeup on my desktop, I never suspend with Steam started, yet starting Steam will get me a "No connection". The funny thing is that even so, it found a new client update, downloaded it, apply it, and restarted to a "No connection".
cloud_log.txt shows that it synced ok.
connection_log.txt shows a mixed bag of:
[1,0] ConnectFailed('Timeout':0) (otherip:27019, UDP)
[0,0] StartAutoReconnect() will start in 5 seconds
[1,58] Connect() starting connection (eNetQOSLevelMedium, someip:27018, UDP)
[1,58] ConnectionCompleted() (someip:27018, UDP)
[1,58] RecvMsgClientLogOnResponse() : [U:1:3xxxxxx] 'Service Unavailable'
[0,0] ConnectionDisconnected('Disconnected By Remote Host') : 'Service Unavailable' (someip:27018, UDP)
[0,0] (null)
Another day, another need to reboot the computer to get Steam working again, the story so far, after the previous comment I've rebooted, Steam started ok, stopped Steam, suspended, woke up after some hours, suspended again for some hours, woke up again, started Steam successfully only to have it lose the connection 30 minutes later and now it won't connect, it believes I have no connection yet it can check for updates ok.
And another thing, what does this in stats_log.txt mean:
[AppID 70] Schema not found on disk
[AppID 70] CAPIJobRequestUserStats - received error 'Failure' (2) from server
[AppID 70] Schema not found on disk
[AppID 70] CAPIJobRequestUserStats - no connection to Steam
Any ideas? Any log you want me to post?
Haven't looked at the code base here on GitHub, but from a UI perspective this is not exclusively a Linux thing. The Steam client does exactly the same thing on Windows - and apparently also OS X - where it refuses to reconnect when reawakening your computer after a sleep period.
Only solution I've found is to restart the client. Seems like a bug that should have been fixed a long time ago.
I got notice of http://www.issteamdown.com and http://steamstat.us in the mean time so maybe this was not a Linux only thing.
Got myself a mac these days, everything is working fine.. with the exception of said issues above. All friends are frozen in the list as if they are playing games at 7 in the morning. Restart the client and its back to normal, this also happens to me more often then not. Mostly dont see anything in the logs though (since it looks like its hanging)
Same deal here. Can't launch games without restarting the client after the computer sleeps. Makes me want to exit Steam whenever I stop using it, which I imagine Valve would not prefer.
I can confirm that this issue persists as of now (OS X 10.9.3).
Same problem. 2008 Mac Pro on ethernet, 10.9.4. So frustrating.
I'm experiencing the same issue on OS X 10.9.4. Steam needs to be restarted after the computer wakes up from sleep or it won't connect. I'm on Wi-Fi.
I'm seeing this issue as well. Steam looses connection after my MBP goes to sleep, and never regains it, resulting in an inability to launch apps and an eternal 'waiting for cloud sync' when I try to exit.
yep, seeing the same problem on OS X, this bug has been around a long time (at the very least 6-12 months)
Same here using a 2012 MBP running 10.9.4. From the looks of this thread, it doesn't seem like Valve cares much though.
@beporter Someone is assigned to this issue it seems. Their backlog must be fat.
I interpret it differently. It looks like it's assigned to a general "triage" account. That combined with the fact that it's been marked as "reviewed" already makes me think they aren't actually concerned with fixing this. The message I'm getting is, "We've looked at this, it's an issue, but nothing we need to have someone (real) address immediately."
It's in the, "we'll get around to it," bucket, which usually means, "we'll probably never get around to it."
An update from my side:
After upgrading to an SSD this problem doesn't occur as often as before. So there might be some sort of timing issue involved.
Well my macbook comes with ssd, i still have this issue. Sometimes i get lucky, i do think with the new icon look update it has reduced but its still heavily present.
Maybe this is related. From the latest beta release notes:
Fix disconnections caused by OS X Mavericks and Yosemite putting Steam into "App Nap" mode, which blocks Steam from receiving chat and other network messages
Does it say any ETA's on it?
Well it seems this just made it to the final release:
Well, just had that problem again. So this is not fixed in the latest beta / final release.
Still occurring on 10.9.5.
Still an issue on Linux, it worked ok after a suspend/resume, got a notice for the Nov. 22 beta update and on restart it can't connect anymore.
@licaon-kter If Steam can't connect on start this seems to be a different problem.
@koraktor: you misunderstood, I said "restart" as in "restart Steam to apply update" (which is the problem in the OP) since it's not needed to restart the whole system for a Steam update.
@licaon-kter I know… when starting Steam. This issue is about Steam losing it’s connection while it’s running, but the system wakes up from standby.
@koraktor: so should I open another issue?
Can confirm this is still an issue on OS X. Really, really annoying. But I guess Valve only has an intern working on this or something... cause even Dota 2 has been busted since the Yosemite update (crashes every single match without exception) and still hasn't been resolved.
I do notice that "sometimes" it restores itself. But most of the times its still bad, i usually notice when starting a game and it just hangs. Then a restart of steam totally helps.
For me, this seems to be finally fixed after the 5/21 update.
It seems to be fixed here, too.
This issue persists for me on Mac OSX Yosemite with the latest Mac Steam client as of today.
I still occasionally have this issue on both my Ubuntu (Unity) and Arch (Gnome) machines; Steam's network connection is occasionally only partially functional (won't sync cloud saves, downloads more slowly, etc.) after waking from suspend.
Same issue for me on Mac OS Yosemite.
Got it too still, rather rarely now but a client restart fixes it at least, it was worse in the past needing a full computer reboot.
I see this regularly as well on 10.11 (and had the same behavior on 10.10, 10.9, etc)
This has been an issue on Mac for as long as I can remember. It happens EVERY single time it wakes from sleep. Steam will say it's online, friends list won't update, no updates client/game come through, none of the pages are responsive; completely dead. Have to quit the application, which then goes unresponsive, which then has to be force quit. After reopening, it runs perfect. That is, until the computer goes to sleep again. Then the above has to done again. This is on the latest OS X [non-beta] and the latest Steam client [beta]. I've had mac's for ~2yrs so this has been a DAILY ISSUE FOR 2 YEARS NOW. This issue does not happen on my Windows laptop or desktop. Only on Mac Mini/rMBP.
Seems to be happening with me, now. Linux Mint 17.3 Cinnamon x64. I'm not sure if it's related to the Linux Mint 17.2 to 17.3 update I did fairly recently or to a new version of Steam.
Steam client application
Built: Dec 14 2015, at 11:19:30
Steam API: v017
Steam package versions: 1450127196
But, while this happened a few times in the past, it now happens EVERY time my system comes back from sleep.
It also happens with me on mac. Every time I wake up my computer from sleep, I have to close steam and reopen it, otherwise it won't connect to internet and won't lunch any game.
Yep, I'm absolutely still seeing the issue on Mac OS X (18-months since my last post about it, everything up-to-date).
I am perplexed as to why it's been so long and Valve still hasn't bothered to fix this. I mean you people are making millions off gamers and you can't fix a simple bug like this?
This thread has been open for almost 5 years already! C'mon!
I had this problem on my last computer, and now it's happening on my brand new computer so I'm no longer convinced that it was something to do with my computer. I've looked online for solutions previously and found nothing. This is the first time I saw this thread, it'd be great to have a solution.
Possibly related to the issue:
https://thesquareplanet.com/blog/the-story-of-a-rust-bug/
Issue still persists in 2017 on Windows 10. This is why competition is A Good Thing.
Having the same issue on Xubuntu 16.04, steam fails to connect and joining any server without restarting steam gets me kicked after a few minutes for a VAC connection error.
Setting myself to offline and then back to online doesn't work as sometimes did on windows, I just remain offline permanently until I restart steam.
Happens to me when one of my hard drive is sleeping (after being idle for a given time).
Part of my Steam library is on that disk, and starting Steam wakes it up. In this scenario Steam takes quite longer to start, and sometimes fails, but not always. What's weird after that is, if I launch a game (Dota 2), it starts, but has no connectivity whatsoever. Dota 2 is not even on that hard drive, it's on a separate SSD (main steam directory). I use the Steam Library Folders, no symlink/junction voodoo in Win10.
I have the same problem and this should not be that hard to fix. This problem is really annoying. Why not fix it or at least set is as a milestone?
If no answer for some seconds test local connection to the internet by trying to reach a steam server, if success: the connection is broken and a reconnect is needed. Or just reduce the timeout... There are so many easy options...
Another idea could be to have a service that periodically logs the time if there are more than x seconds gone from the last to the current sample, the computer just came from standby and the connection needs to be checked...
I have this issue to. Its pathetic. Steam will auto update my games, I go to play them and while in game it says its not connected. Even after 20 minutes of having a restored connection it still wont see it as being online. This bug is 5 years old :(
Same issue, 6 years later. How about a fix boys?
I have the same issue, and it makes the Steam Link experience much less polished than it could be.
I have a few PCs and I set them to suspend with Steam Big Picture maximized when I'm not using one of the machines. When I want to play a game on the TV, the Steam Link sends them a Wake On LAN packet which starts the computer up, and let's the Link reconnect to Steam on my PC.
And it works great, except that my Steam Cloud connection on the PC goes away because of this network issue, which results in games taking forever to launch while the network stuff times out.
The Steam Link experience would be so much smoother with this fixed.
2017, and the issue still exists. I thought at first it was because some of us had renamed the libstdc++.so shared object in order to get the client to work, (the rust bug suggests including a rewrite for res_init for hostlookups) but mine has reverted long ago, from updates. And hasn't needed to be removed for some time.
So since it is now included fine, someone just needs to work out the kinks coming from an improper call to res_init for Ubuntu/Mint systems maybe?
if it was any harder than exiting the client and making sure all the steamapi backgrounds close properly, and restarting... I might consider delving into the code myself. Think maybe you guys want to escalate this issue? It's been kinda a LONG haunt now.
I'm more of a mind to hope that a Valve employee will read the comment about Steam Link, hope that they see it in their business interests to fix it to enhance the Steam Link experience, and prioritize the issue. :)
Not trying to get off on a tangent about Steam Link, but it is a pretty good experience (YMMV) except for this issue which is an irritant.
If read the comment about UDP, I guess it's just a firewall issue.
As udp is connectionless, it will never ever get teared down due to inconsistent ports or sequence id's.
But in the mean time the firewall might have a different opinion about said "connection" than the steam client.
What kind of router firewalls are involved? Has anyone tried to tcpdump the issue on the firewalls? Just to see what's going on...
it is not only issue of linux version. right now i am in windows 10, after sleep and wake up
Error
There was an error communicating with the Steam servers. Please try again later.
Retry
i didn't had this problem before, it started to appear only month or so ago. now i have it in both linux and windows system (on the same pc and same network)
This bug is from 2012, 6 YEARS AGO, and still not addressed. Also it doesn't reconnect when you switch WiFi networks. I was playing a game of dota 2 and I needed to switch to other WiFi network because the current stated lagging, so I switched network and reconnected to the game. a few minutes later, I'm kicked out of the game, because of 'Failed Steam Login'. So I needed to close dota 2, close steam and re-open it, start the game and then reconnect. This is so annoying and time-consuming.
Meanwhile on Windows, you can just click reconnect and done. Resuming from sleep or switching networks reconnect to Steam in ~10 seconds, while on Linux, Friends state ('Online', 'In-Game'...) gets stuck for ~1 hour before it reconnects and start being normal.
The inaptitude of the Valve software engineers is baffling to me. How can you not debug and fix this.
@kassybas Because you can't answer "or else what?".
You're welcome.
Installed Linux two days ago, and Steam yesterday. During the night I put the PC to sleep, and when I woke it up a couple of minutes ago I noticed this same issue. I've tried to download CS:GO, and got the timeout message two times before I lost the patience and just restarted Steam.
The thing is: this isn't the kind of issue that prevents someone from playing, but it is at least uncomfortable.
I don't get upset with it as such.
It's just that if steam didn't have issues after waking up from sleep, I could have such a seamless Steam Link experience! The Steam Link will send a wake-on-LAN package to your PC which is in sleep mode (I suspend to RAM). And after it comes back up, I can play my games, but before they'll launch I have to wait through a network timeout while the game tries to talk to Steam Cloud to sync itself, but can't because of the network issue.
I have wired LAN in the house, and my Steam Link-PC experience is great. I just wish I could have this additional convenience if the Steam Client would reconnect after sleep.
From: Renato [email protected]
Sent: Wednesday, March 21, 2018 5:30 PM
To: ValveSoftware/steam-for-linux
Cc: jonbitzen; Comment
Subject: Re: [ValveSoftware/steam-for-linux] Steam: Partially Fails to Connect to Internet after Waking (#474)
Installed Linux two days ago, and Steam yesterday. During the night I put the PC to sleep, and when I woke it up a couple of minutes ago I noticed this same issue. I've tried to download CS:GO, and got the timeout message two times before I lost the patience and just restarted Steam.
The thing is: this isn't the kind of issue that prevents someone from playing, but it is at least uncomfortable.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/ValveSoftware/steam-for-linux/issues/474#issuecomment-375102541, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKyELFlMytInQywC0xvns49lYd5UP8Peks5tgsaKgaJpZM4AVdyW.
Same years-old problem here. Occasionally I have the same problem when resuming on Windows 7, but on Linux it happens almost every single time.
I too am having this problem EVERY DAY (on linux btw). It's infuriating, especially since it's a known issue since 2012.
I am also experiencing this issue. Usually, about half an hour after waking up, Steam is able to reconnect. Too bad that this is still not fixed after all those years.
Every day issue for me on arch linux too. After I wake PC, I have to close steam and run it again.
I've noticed recently this is equally an issue on Windows 7. I have to close steam and start it again, just like on Linux.
It could even be that the original poster died, since he has 6 years of no activity in his profile. (i moved back to windows for gaming only because of this issue)
Same problem :(
I had the same issue today under the latest Windows 10 when resuming from hibernation.
I don't think that it happens everytime on Windows, but it's cumbersome, if you never can be sure if you are actually really "online" this time, or if it just seems to be that way.
Apart from the problem (occasionally) happening under Win 10, it's happening to me on Linux (Solus) every single time.
I am using Network Manager and I have always had this issue with the Linux client not reconnecting after system resume. I used to have the Metro skin installed which had a "Restart Steam" option in the menu which I would use to work around the problem.
The default Steam skin doesn't have a restart option though, so now I have to quit it and start it up again to get reconnected.
Is there any command line option for steam, or a signal to send to the process which will force it to reconnect? We could then use this in a script which is run by NetworkManager when the network reconnects.
Still an issue even on steam beta. Seriously Valve on error just tell the app to re-start it's networking. So I don't have to restart your App. Simple fix even form a programming perspective.
Same bug, every time suspend/resume is used and on Windows as well as Linux. Games hang when launching because they try to synchronise save states with Steam Cloud. The app is not capable of reconnecting to the server on resume, which is kinda ridiculous as literally every other app does this.
I'm having the same issue, and given that this thread is 6 years old i pretty much think it's going to stay that way.
Ubuntu 18.04 on an HP 14 laptop, in case it helps.
See, this is weird because I've never had this issue before. But starting a week ago, all of a sudden it's happening. Running Antergos Linux Steam Runtime.
+1
Same issue here running Manjaro Linux.
Same issue here, Fedora 29. Steam doesn't reconnect properly after the computer wakes up from sleep.
Steam client application
Built: Jan 4 2019, at 23:23:48
Steam API: v018
Steam package versions: 1546909276
the weird issue is, after resume from sleep steam client can download (update, queued game) automatically (steam can connect internet), but if i try to launch game it fail sync with steam data bla3, need to restart client to behave normal again.
Gentoo Linux same issue.
Steam client application
Built: Jon 30 2019, at 23:03:27
Steam API: v018
Steam package versions: 1548894698
emerge --info, eix-installed all
Making matters worse, whenever I accidentally hit "Remember Me" it crashes on first automatic login (next time one opens steam).
Doesn't reproduce on the Epic Games Store 😎
Doesn't reproduce on the Epic Games Store sunglasses
Unfortunately this issue is about Steam for Linux and not a platform that doesn't even support Linux yet. I don't see how that is even relevant in the slightest apart from trying to start some Epic Store vs Steam war.
Seems this issue has been open for 7 years with near zero feedback from the dev team it might as well have some humor in it.
Seems this issue has been open for 7 years with near zero feedback from the dev team it might as well have some humor in it.
I agree it's a "bit" sad nothing is being done, I guess I'm just tired of those Epic Store vs Steam wars... Or maybe it's just a bit too early and I'm turning old and cranky. ;)
Same with me here, like Valve devs can't fix this/too lazy to fix this annoying bug
Same bug on Linux Mint 19.1. Really nice job, Valve!
G'day everyone!
Today's Steam Beta contains changes to the networking code that address this issue, although I suspect there may be multiple underlying causes, so we're hoping for feedback on how well it's working. The Steam client can still take a few seconds to notice a network change, but it should be well less than a minute.
So we don't overwhelm everyone on this ticket, if you find today's beta fixes things this bug for you, then please thumbs-up this post. If the issue still persists and its exactly the same as before, then please thumbs-down this post.
Many thanks!
~ Paul
Today's Steam Beta contains changes to the networking code that address this issue, although I suspect there may be multiple underlying causes, so we're hoping for feedback on how well it's working. The Steam client can still take a few seconds to notice a network change, but it should be well less than a minute.
Even a minute is better than completely unable to reconnect, I am gonna attempt to update and test it!
Edit:
I just did some testing, after receiving the 15 May update, and I did notice some improvement. I basically tested the following: turning wifi off and on again and connecting to VPN, before I had to restart steam after I got the "message failed to send" notification.
But now it detected after a few seconds it was disconnected and then reconnected resulting in me being able to send messages again.
I have tested a few times today after my PC had been to sleep and steam does seem to be reconnecting OK now within a minute and everything works properly after that.
I assume the minute is because steam is periodically checking something to see if it needs to reconnect? If steam accepted a signal which would force it to reconnect, or a command line argument, then a NetworkManager dispatcher script could be used which would tell steam the network has just reconnected. Obviously that would only work for people using NetworkManager, but the ability to force steam to reconnect by a command would be useful for other people too.
But yes, waiting a minute isn't that long :)
I assume the minute is because steam is periodically checking something to see if it needs to reconnect?
The time is a cautious balance between dropping connections too soon (which could result in flapping on a poor connection), waiting too long for a lost connection to return (which gives the pain point we've seen in this issue), and me not wanting to break Steam. :)
The current timing values are over 9000ms, but this isn't even their final form.
It's working as it should now. Reconnects after a few seconds.
Really? I will have to test this... it has been so long I just always assumed it would fail.
Seems fixed like maybe we can finally close this one!
I'm on Ubuntu 19.04 and after waking from sleep, it almost always has issues with reconnecting to the internet. I have to exit steam, then open it again.
Fixed for me in the recent betas. Ubuntu 19.04.
I'm on stable. Have the fixes for this issue been pushed to stable?
@dasunsrule32 : It's only in the beta client for now, but since it seems to be working you can expect it to be folded in with the next stable release.
@pjf-valve : makes sense, thanks for the update!
@pjf-valve
From changelog 17th june 2019:
Improved the client's responsiveness to network changes
Is this fix?
@ivnish looks like it, it works for me now in stable version (after few refreshes).
This is working for me in stable now. I have Steam package versions: 1560549607.
Fixed for me now.
I haven't had a problem for awhile now, looks like this might have gotten some love <3
Closing as fixed.
Should we make a honorable mention for this on https://developer.valvesoftware.com/wiki/Valve_Time ?
Should we make a honorable mention for this on https://developer.valvesoftware.com/wiki/Valve_Time ?
Sure, why not?
This issue is still very much alive on Arch Linux. After waking from suspend, no games will launch, indefinitely, until reboot.
Works for me on Archlinux.
Works for me on Archlinux.
Reading the above comment history, it's difficult for me to determine what actually fixed this issue for the users here. Is it some kind of network management thing? My systems connected via ethernet can get away with just dhcpcd, but I digress. I feel like I'm making shots in the dark. For instance, the issue presents itself on both i3-wm and gnome.
Is there something about your system that you reckon might be affecting this issue? I guess we can rule out Arch Linux in general. I suspect the problem can be reproduced on other distros, but again, I have no idea how.
@laftur
it's difficult for me to determine what actually fixed this issue for the users here
A patch was released (see this message) that fixed the network connectivity problems after waking from sleep.
After waking from suspend, no games will launch, indefinitely, until reboot.
Do you also have this problem after restarting Steam? The original report (which was also my experience with this bug) stated that restarting Steam fixed the problem. If not, you probably have a different problem than this (already closed) issue, and I'd suggest opening a new issue. Hopefully you can find some more information about what is happening, to help pin down what the problem is.
Do you also have this problem after restarting Steam? The original report (which was also my experience with this bug) stated that restarting Steam fixed the problem.
Restarting steam doesn't fix the issue. Even if I close steam before suspending, then start steam again after waking, no games will launch. I thought such an adjacent issue would have been investigated alongside this one. If you really think it's unrelated, I'll start another issue thread.
Upstream links
- ValveSoftware/steam-for-linux/issues/474x2 2020-07
I've noticed that, several times, after I have woken my computer up from "sleep," Steam will have difficulty connecting to the internet. Browsing and everything else on the PC works fine, but Steam will say that it is "Unable to connect to the server" when I attempt to load the store page. Multiple refreshes and waiting a few minutes can usually resolve the issue.
Additionally, this gets in the way of launching games sometimes. For instance, right now, I am sitting waiting on Killing Floor to launch. The pop-up window says "Preparing to Launch Killing Floor," but it generally just sits there indefinitely, doing nothing.
If I attempt to launch the game directly from it's working directory, it starts, but I receive a message about how multiplayer won't work, because Steam isn't running or I don't have an internet connection.
Restarting Steam seems to resolve this.