-
Notifications
You must be signed in to change notification settings - Fork 70
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
CS:GO Failed to reach any official servers #112
Comments
Steam self-updates independent of the Flatpak updates at any rate |
I'm aware of that and I did receive the update that is supposed to fix the problem (which it did for seemingly anyone else), but it didn't fix it for me. That is why I suspect the flatpak package to still cause this. |
The curious bit is the problem was externally reported only with beta Steam, not proper Steam. You're running latter, right? |
The issue has been introduced with the chat beta and has finally been fixed with the stable update. I've updated to the stable version, yes. |
Given the workaround sets LC_ALL=C this seems to be a locale problem, so is it possible the flatpak container might be missing some locale information? |
Maybe although it sounds like the fix included changing some configuration file not to contain special characters. You could try running command locale both outside and inside Flatpak sandbox. You can get shell in latter through |
|
LC_ALL is "never" supposed to be set. It's a mass override. Normally LC_* values are handled individually. |
Setting steam up freshly did not help, so it's not some messed up file from the beta. |
In theory it's simple to add environment override into the app but LC_ALL=C is such a hammer solution that I don't like doing that without further information on what exactly causes this. It could very well have side-effects |
Can you confirm through relevant logs and md5sums that this is actually same issue and doesn't just look the same? |
I was discussing with upstream and LC_ALL=C should be a no-op assuming up-to-date Steam so something is off here. |
Did you by the way touch contents under .var/app when setting up Steam freshly? |
I completely agree.
Which logs/files are you thinking of? I can not really guarantee it's the same issue, but the behavior is exactly the same and the same workaround works, so I'm pretty certain. I start CS:GO, try to search a competitive game and after a few moments I get a message telling me it cannot reach official servers. From the upstream reports this also happens for Dota in case you want to test anything.
Yep, nothing changed with the new version.
I completely removed Btw I'm also not using any crazy locale on my system: |
Well, the Valve dev said Steam now ignores locale for this purpose so there's something weird going on |
I'm wondering if anyone else has the same issue with the flatpak or if the problem exists only on my system. Do you have CS:GO or Dota to test this as well? |
Nope, I don't have either in my catalogue |
I'll try to reproduce on a few other systems and get back to you. Dota would free AFAIK and I'd be open to sponsor a CS:GO key to get this fixed. |
I can take a look at Dota later if it's free. What exact locale did you have again? |
That would be great! I use locale |
Could you please also attach output from help->about steam? Also, Dota or Dota 2? |
That is actually interesting. The version number is significantly higher than mine. I wonder if that's still a beta build since I've been repeatedly wiping my installation to test a cloud sync bug so I should have up to date Steam |
I have also checked with a mate, he has the same problem. |
Also why I grew suspicious is your version is identical to #91 in logs |
Do you mean my steam thinks its "out of beta" but it's really not? The automatic updates came up for me. I tested the early beta of the chat feature, then disabled the beta as I found out about this problem and then it recently updated normally on the stable channel and I received the new chat stuff together with this bug. So it updated from the "good" old stable version to the "broken" new version by itself. Haven't mentioned here so far: My host system is Archlinux with Flatpak 0.99.3 |
The problem is I haven't found a good source for the information of what is the up to date version in stable |
I could try to install Steam directly on my system this evening to test if it's also happening there and I can also post a screenshot of the about screen then. |
Try with:
|
Freedesktop runtime was just updated, might be worth it to retest |
With the new runtime it finally works. |
How can I update to the enw runtime? I have do |
It should update automatically. If you're still having issues, I would have to ask you: does your Steam chat work? Does your wishlist work? |
I have still matchmaking issue, and it work with the native version Steam + CSGO logs: https://pastebin.com/1qg2QgXC |
@Amosar can you please update and retry now? |
I still have this issue with the latest patch :'( |
You're running steam wrong and bypassing steam-wrapper |
How do I need to run it? |
flatpak run com.valvesoftware.Steam |
:/ I have tried with this command but it still doesn't work. |
I can see from your latest log that the timezone quirk is being applied |
yep, the issue is back. |
Is there a good guide somewhere on how to use flatpak-bisect ? Or do you already know which verison introduced the problem? |
No and given how intensive data relocations have been done recently, bisect would be hard. |
I'm using a mix of en_US.UTF8 and de_DE.UTF8 on my system, if that's relevant:
Might this be related to some kind of number format problem? |
Could you please test if setting LC_NUMERIC=C is enough to fix this issue? |
This came up in possibly related issue. If it does, I might consider applying that as a workaround in general. That should be largely harmless if it fixes the issue, may just make numbers look a bit non-native to some users |
Does this still reproduce? |
Works now. |
(Also posted this in #1678 ValveSoftware/csgo-osx-linux) I still have this issue on Linux. OS: Ubuntu 18.04.2 64-bit. Steam API: v018 running steam with flatpak:
The MD5 checksum of I have tried solutions posted elsewhere such as going to CSGO properties > LOCAL FILES > Verify Integrity of Game Files. 1 file fails the test and is downloaded. This doesn't solve the issue. This problem occurs with any configuration of the firewall (UFW). Currently is set to deny in and allow out. Another piece of information is that this occurs randomly (I had been able to play in multiplayer for the last few weeks and suddenly couldn't). This problem persists even if I launch steam without launching any other application, and no application running in the background except those that run in a vanilla Ubuntu install. I don't have any skins installed, and this problem persists if I reinstall steam. |
Could you post a first 20 or so lines of log when you start Steam? |
It seems that it's working today! (can't reproduce this issue. Yesterday February 27, 2019 it wasn't working as I described in my post). Anyway, here's the output:
|
Upstream issues:
The upstream issues mention, that the issue is solved by the latest stable update and people confirmed it working after the update release. I have updated my steam in flatpak to the latest release, but the issue persists.
It still only works, as suggested in the issues, by supplying
--env=LC_ALL=C
.Not sure if this is the right place to report this.
The text was updated successfully, but these errors were encountered: