search

ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.25k stars 175 forks source link

Steam does not connect on kernels newer than 2019-06-17 #6326

Closed killerrabbit closed 5 years ago

killerrabbit commented 5 years ago

Your system information

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist

When starting steam, after logging in and authenticating past steam guard, it hangs on "Connecting to steam account: (account name)." Sometimes it will change to "Updating Steam information" with an empty progress bar.

After a while, it will give a dialog box saying that says "Could not connect to Steam network."

Output of console: https://gist.github.com/killerrabbit/94419ec85564e248c044d21e0fd961b3

Steps for reproducing this issue:

  1. Install Steam
  2. Attempt to log in
jonlap commented 5 years ago

I have this same problem in Arch Linux with the exception that I am opted into Steam client beta. This issue started few days ago, after system update, on installation where Steam client has been working OK before.

I have removed my ~/.steam and ~/.local/share/Steam and tried again with no luck. I also tested with flatpak current stable, same results. Meanwhile, Steam (flatpak stable) is running fine on my laptop with Void Linux. Both of these machines are in same network.

Console output

neirenoir commented 5 years ago

Having a very similar issue here on NixOS after the latest system update. Main difference is, in my case, it manages to log in around 10% of the times. It also says "Updating User Configuration..." without an empty progress bar in the second prompt, which appears 100% of the time if it does not manage to connect. Keep trying to log in, maybe even kill the process while it is booting so it attempts to check the integrity of the installation (it probably is irrelevant, but the times it has worked for me, this was the case)

EDIT: rolling back to a previous NixOS generation (kernel 5.1.5) makes Steam work well. Executing previous versions of the Steam package within the latest NixOS generation (kernel 5.1.11) does not work. This makes me think there is some kind of library, or the kernel itself, interacting erroneously with the same Steam package. @killerrabbit, @jonlap, did you update your system as of lately? Are you using any wrapper programs when launching Steam?

blastermaster77 commented 5 years ago

Same problem with ubuntu 19.04 after update, Could not connect to Steam network. I tried on my laptop and same thing sad... my console output

EDIT: woke up today and tried to long in on my laptop and it did log in, tried on my desktop and same error. weird.

ghost commented 5 years ago

I am also experiencing this problem on both Arch Linux and Kubuntu. Both OS run on the same exact hardware. Meanwhile, a Windows 10 PC on the same network works fine with Steam.

On both Kubuntu and Arch Linux, I was able to login and receive a Steam Guard password through email to authenticate on a new machine. At this point the error occurs.

EDIT: I also tried setting up and using steam-native, but got the same results.

iswritergeek commented 5 years ago

I also have this problem on my Arch install. Been happening for two days now, ever since I rolled over to the new kernel. There also seems to be a problem with the Breeze plasma theme and the way the new kernel does networking, as can be seen here in my console output.

I'm running the arch linux-lts, btw. I've had no problems connecting up till today using the steam package.

killerrabbit commented 5 years ago

I downgraded my kernel from 4.9.0-9 to 4.9.0-8 and steam is now working correctly.

Something in the kernel update broke it.

MarkDDR commented 5 years ago

I had this same problem on my Arch Linux as well, but I was able to actually start steam by directly launching a game I had installed, with the command steam steam://rungameid/440 (which launches Team Fortress 2). I would test this further but after this I seem to be able to launch steam normally without any issues.

Xanderful commented 5 years ago

Same issue here, steam started fine until I purged and re-installed for another issue on Ubuntu 19.04 vanilla edition. Same computer, steam on Widnows starts fine and on another edition of Ubuntu running Mate 19.04 same. I am running 5.0.0-17-generic on the version that is not working.

Hartmnt commented 5 years ago

I have the same problem running Ubuntu 19.04. The issue apparently started after the upgrade to kernel version 5.0.0-17-generic a few days ago for me as well.

I maybe have another insight though:

I'm running a strict multi-user setup which basically means that every major application has its own user or user group (leaving some details out). This also applies to steam in my case. One of the first thing I tried was starting steam from my main desktop user, since the actual steam installation is user-specific in the respective $HOME folder. Steam downloaded its bootstrap or whatever and asked me to login and provide the Steam Guard Email authentication thingy. And it worked. And it continues to work consistently with that user.

This of course means that i have no games or custom configuration in that steam instance but Steam at least starts. It seems like a complete purge and re-installation could possibly fix the problem, but I'm not sure about that. I really don't want to reinstall Steam and/or the Steam games for my steam-user and I'm not sure that would even work, so I'm hoping there will be another solution.

Edit: Another thing: If you go into your ~/.steam/steam/config folder and edit the loginusers.vdf using a text editor, you can force steam to start in offline mode, allowing you to at least play the steam games not requiring you to be online.

Seegras commented 5 years ago

Same here on Debian Unstable with mainline (not Debian) kernel 5.1.12 (and 5.1.11 also). NVidia drivers 430.26. Login works, but after that I get "Could not connect to Steam network.". I also get that when starting it with the parameter "-tcp". And I also deleted steam (except steamapps) and reinstalled. No avail.

My assumption is that some security-upgrade, probably in the kernel, which was important enough to get backported might be the trigger for steam not working anymore.

I think it's the networking in the kernel:

linux (4.9.168-1+deb9u3) stretch-security; urgency=high

[ Salvatore Bonaccorso ]

  • tcp: limit payload size of sacked skbs (CVE-2019-11477)
  • tcp: tcp_fragment() should apply sane memory limits (CVE-2019-11478)
  • tcp: add tcp_min_snd_mss sysctl (CVE-2019-11479)
  • tcp: enforce tcp_min_snd_mss in tcp_mtu_probing()

  • tcp: fix fack_count accounting on tcp_shift_skb_data()

    [ Ben Hutchings ]

  • tcp: Avoid ABI change for DoS fixes
  • mm/mincore.c: make mincore() more conservative (CVE-2019-5489)
  • brcmfmac: add length checks in scheduled scan result handler
  • brcmfmac: assure SSID length from firmware is limited (CVE-2019-9500)
  • brcmfmac: add subtype check for event handling in data path (CVE-2019-9503)
  • tty: mark Siemens R3964 line discipline as BROKEN (CVE-2019-11486)
  • coredump: fix race condition between mmget_not_zero()/get_task_mm() and core dumping (CVE-2019-11599)
  • net: rds: force to destroy connection if t_sock is NULL in rds_tcp_kill_sock(). (CVE-2019-11815) (Closes: #928989)
  • ext4: zero out the unused memory region in the extent tree block (CVE-2019-11833)
  • Bluetooth: hidp: fix buffer overflow (CVE-2019-11884)
  • mwifiex: Fix possible buffer overflows at parsing bss descriptor (CVE-2019-3846)
  • mwifiex: Abort at too short BSS descriptor element
  • mwifiex: Don't abort on small, spec-compliant vendor IEs

  • mwifiex: Fix heap overflow in mwifiex_uap_parse_tail_ies() (CVE-2019-10126)

    Sun, 16 Jun 2019 15:38:39 +0100

blastermaster77 commented 5 years ago

The weird thing is that both my laptop and desktop have the latest updates and one connects now and the desktop does not. Yesterday both could not connect to steam network. I dont know what is going on. Hope they fix it soon, its driving me nutz!

Same here on Debian Unstable with mainline (not Debian) kernel 5.1.12 (and 5.1.11 also). NVidia drivers 430.26. Login works, but after that I get "Could not connect to Steam network.". I also get that when starting it with the parameter "-tcp". And I also deleted steam (except steamapps) and reinstalled. No avail.

My assumption is that some security-upgrade, probably in the kernel, which was important enough to get backported might be the trigger for steam not working anymore.

I think it's the networking in the kernel:

linux (4.9.168-1+deb9u3) stretch-security; urgency=high [ Salvatore Bonaccorso ]

  • tcp: limit payload size of sacked skbs (CVE-2019-11477)
  • tcp: tcp_fragment() should apply sane memory limits (CVE-2019-11478)
  • tcp: add tcp_min_snd_mss sysctl (CVE-2019-11479)
  • tcp: enforce tcp_min_snd_mss in tcp_mtu_probing()
  • tcp: fix fack_count accounting on tcp_shift_skb_data()

[ Ben Hutchings ]

  • tcp: Avoid ABI change for DoS fixes
  • mm/mincore.c: make mincore() more conservative (CVE-2019-5489)
  • brcmfmac: add length checks in scheduled scan result handler
  • brcmfmac: assure SSID length from firmware is limited (CVE-2019-9500)
  • brcmfmac: add subtype check for event handling in data path (CVE-2019-9503)
  • tty: mark Siemens R3964 line discipline as BROKEN (CVE-2019-11486)
  • coredump: fix race condition between mmget_not_zero()/get_task_mm() and core dumping (CVE-2019-11599)
  • net: rds: force to destroy connection if t_sock is NULL in rds_tcp_kill_sock(). (CVE-2019-11815) (Closes: #928989)
  • ext4: zero out the unused memory region in the extent tree block (CVE-2019-11833)
  • Bluetooth: hidp: fix buffer overflow (CVE-2019-11884)
  • mwifiex: Fix possible buffer overflows at parsing bss descriptor (CVE-2019-3846)
  • mwifiex: Abort at too short BSS descriptor element
  • mwifiex: Don't abort on small, spec-compliant vendor IEs
  • mwifiex: Fix heap overflow in mwifiex_uap_parse_tail_ies() (CVE-2019-10126)

Sun, 16 Jun 2019 15:38:39 +0100

blastermaster77 commented 5 years ago

I copied the .steam folder from my laptop that does login and it fixed the problem this is weird.

EDIT: I stoped working again

jkaart commented 5 years ago

I have same problem with fresh installed 64-bit Ubuntu 18.04. Edit: It works with 4.18.0-15 kernel no problem but with newest 4.18.0-22 version not work.

jonlap commented 5 years ago

Downgraded kernel from 5.1.11-arch1-1-ARCH to 5.1.8-arch1-1-ARCH (which is the latest previous version I had in pacman cache) and Steam now works again. Changed nothing else so yeah, something kernel related.

Seegras commented 5 years ago

Valve, please fix steam. Going back to a kernel which has at least 13 known security vulnerabilites (all the changes denoted with CVE's are security fixes) is not an option.

YevPo commented 5 years ago

Running steam from terminal with -tcp param fixed this problem for me:

$ steam -tcp
dhollinger commented 5 years ago

I'm on Pop!_OS 19.04 (desktop optimized Ubuntu) with a 5.x kernel and haven't had any problems with steam. Been on this kernel for a few weeks now.

Seegras commented 5 years ago

It's not just a 5.x kernel, but probably 5.1.11 or newer (or an earlier one with some security fixes backported). Apparently 5.1.8 works, 5.1.9 and 5.1.10 might also.

XakepSDK commented 5 years ago

Linux arch 5.1.11-arch1-1-ARCH Steam: Jun 17 2019, at 23:31:27 Steam works fine. Also 1 or 2 days earlier, steam asked me to log-in manually.

ugly95 commented 5 years ago

I'm glad people are starting to notice this. It's been happening to me since Monday when I got the 5.0.0-17 kernel update and I hadn't seen anyone comment on it and thought I was the only one.

As others have said, rolling back to an earlier kernel version works (in my case to 5.0.0-16) resolves this issue.

My console output ends at 

Running Steam on linuxmint 19.1 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
[2019-06-18 19:48:15] Startup - updater built Jun 17 2019 23:31:08
[2019-06-18 19:48:15] Verifying installation...
[2019-06-18 19:48:15] Verification complete
STEAM_RUNTIME_HEAVY: ./steam-runtime-heavy
[2019-06-18 19:48:41] Shutdown

The google results for issues with not being able to connect suggest deleting ~/.steam, which resulting in Steam re-downloading and installing and successfully connecting. But after closing Steam and trying to login again, it starts failing again.

Another suggestion was to run steam --reset. Not sure if it's related, but I get Error: Couldn't find bootstrap, it's not safe to reset Steam. Please contact technical support.

Running Steam through Wine also connects successfully.

XakepSDK commented 5 years ago

Linux arch 5.1.12-arch1-1-ARCH Works fine! Note: i didn't log out, but just exit / start steam 3 times.

blastermaster77 commented 5 years ago

I can confirm that rolling back to an older kernel fixed the problem, in my case I installed 5.0.0-13-generic on ubuntu 19.04 if I update to the newest kernel 5.0.0-17 the problem starts again, waiting for a fix thanks. I also noticed that when it is installing the update on the new kernel it stops and it does not install it, hope that helps.

niarbeht commented 5 years ago

It's happening to me whether I use steam -tcp or not. steam -tcp does not appear to fix the issue on Arch with kernel 5.1.12-arch1-1-ARCH. I have tried steam --reset and deleting the contents of ~/.local/share/steam

alosarjos commented 5 years ago

Are we sure it's something kernel related? Haven't had any issues in the last weeks and I check for updates daily.

Arch Linux x86_64 / Kernel 5.1.12-zen1-1-zen Steam beta client

You guys have any kind of network config on your machines?

SergeyLatyshev commented 5 years ago

After installing 5.1.11 (and 5.1.12 today) with ukuu, I have this problem too. Steam is in autorun, and never connect at the first try, only after I relaunch it. Sometimes it takes several tries to launch it successfully.

darkpumpkins commented 5 years ago

Have you tried into a terminal ? export STEAM_RUNTIME=1 steam it solved my issue on my ubuntu 19.04.

emmecii commented 5 years ago

Can this issue happen with the HWE kernels of Ubuntu 18.04?

EDIT: Someone pointed out can be related to the recent Netflix bug discovering to network stack

https://www.reddit.com/r/linux_gaming/comments/c37lmh/psa_steam_does_not_connect_on_kernels_newer_than/erp83w5/

https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SACKPanic

dennis1248 commented 5 years ago

I have a very similar issue which recently appeared and is most likely related, Steam struggles to connect to the Steam friends network after it has started. But it does manage to connect after 10-20 seconds and a retry.

I use Void Linux btw, I believe the issue first appeared when I updates to kernel version 5.1.11.

On Fedora running kernel 5.1.11 the issue is not present nor do I experience any other bugs/issues.

otvv commented 5 years ago

Can confirm, kernel 5.0.0-13-generic works for me, but 5.0.0-17 don't. And the strange thing is: When I'm on kernel 5.0.0-17 I can't login on my main Steam account (fails on updating Steam information) but when I try to login on a empty account it works just fine. (Ubuntu 19.04)

mirh commented 5 years ago

If you have some spare time, https://wiki.archlinux.org/index.php/Bisecting_bugs_with_Git

MaxXor commented 5 years ago

No issues for me on Linux 5.1.12-arch1-1-ARCH #1 SMP PREEMPT Wed Jun 19 09:16:00 UTC 2019 x86_64 GNU/Linux.

debiangamer commented 5 years ago

No Steam problems with the latest AMD wip kernel : Host: ryzenpc Kernel: 5.2.0-rc2+ x86_64 bits: 64 Desktop: Xfce 4.13.2 Distro: Debian GNU/Linux 10 (buster)

Never Steam or other problems with this kernel.

blastermaster77 commented 5 years ago

Do you clean install steam? If you don't you won't see the problem.

On Fri, Jun 21, 2019, 3:59 AM Sergey Latyshev notifications@github.com wrote:

After installing 5.1.11 (and 5.1.12 today) with ukuu, I have this problem too. Steam is in autorun, and never connect at the first try, only after I relaunch it. Sometimes it takes several tries to launch it successfully.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/steam-for-linux/issues/6326?email_source=notifications&email_token=ACHAHPX43QOBP52Q32HGYJDP3SC5XA5CNFSM4HZOAO32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYHX2PA#issuecomment-504331580, or mute the thread https://github.com/notifications/unsubscribe-auth/ACHAHPRL3XQUZ7LAPWUBFYLP3SC5XANCNFSM4HZOAO3Q .

AngryPenguinPL commented 5 years ago

Works for me on OpenMandriva Cooker with kernel 5.1.12. Tested on two PC and notebook.

ghost commented 5 years ago

Did a clean build of Void Linux on a different laptop then what I used for my previous attempt. Void uses kernel 4.19.53, which has the new tcp stack changes. Had the same issue out of the box

Markaos commented 5 years ago

Ubuntu 19.04, kernel 5.0.0-17-generic: the login works randomly for me - Steam completely refused to start twice, then started but with Friends offline, then connected to Friends after I clicked the Reconnect (or whatever the text is) button. Browser and Steam Chat app on the same network worked just fine, steamstat.us reported no problems, so it should be this problem

jonlap commented 5 years ago

Void uses kernel 4.19.53, which has the new tcp stack changes. Had the same issue out of the box

I have maybe few weeks old Void install, kernel 4.19.51_1, and clean install of Steam. Steam is working (for me at least) with this kernel version. Anyone have time to bisect as mirh already suggested?

JayGuerette commented 5 years ago

Fedora 30, kernel 5.0.9-301 and 5.0.16-300. Steam works, but streaming stopped working. Tried multiple computers. It executes the game on the remote computer, but displays a black screen and after a bit says "couldn't connect to remote computer"

parasense commented 5 years ago

Fedora 30, fully updated as of Fri Jun 21 2019 using distro kernel "5.1.11-300.fc30.x86_64" works perfectly fine. I'm able to start the Steam client, launch Team Fortress 2, and play the game like normal. No issues what so ever. Tested using an Intel NUC Hades Canyon (NUC8i7HVK) if that helps.

EDIT: Also, this was using the Steam client from Flathub, also fully updated.

garpu commented 5 years ago

I'm using 4.19.53, and no issues connecting to Steam. (Slackware current.) Specific kernel config that's causing the issue, as well?

jonlap commented 5 years ago

Specific kernel config that's causing the issue, as well?

I guess it's possible, although there are people with same kernel version and same distro (and thus same kernel config) as I have reporting Steam works for them.

Chiitoo commented 5 years ago

Same config, probably, /if/ they didn't build their own kernel. :]

This may be even farther fetched, but... it isn't IPv6 related again is it? (Probably not.)

I, too, am using the 5.1.11 Linux kernel currently, on Gentoo, and I have IPv6 disabled everywhere (including the kernel) since my ISP does not provide it at all still.

Steam works for me, though I feel like the start-up time is longer than before (past 40 seconds). I also did have a single failure while connecting some days ago, but I forget if it was before or after switching to 5.1.11... might be completely coincidental.

jonlap commented 5 years ago

This may be even farther fetched, but... it isn't IPv6 related again is it? (Probably not.)

I tried disabling IPv6 at some point, didn't help.

urbenlegend commented 5 years ago

I think the latest Steam Client update fixed this already? I have 3 Fedora machines currently. Two of them I use very often for gaming and I had already updated them to the latest Steam Client prior to upgrading them to kernel 5.1.11. Steam logged in just fine on these two machines post-kernel update.

Later, I tried to login into Steam on my 3rd machine, a laptop. This one I don't use for gaming very often, and I had upgraded to kernel 5.1.11 before updating Steam. Steam failed to login consistently on this machine. I then ran steam --tcp which allowed me to login and update. After the update, the problem no longer occurs.

dearlygparted commented 5 years ago

I haven't had any issues connecting to Steam on Arch Linux. Currently running this kernel:

$ uname -r
5.1.12-arch1-1-ARCH
sgtnasty commented 5 years ago

I had the same problem yesterday on neon (18.04) and decided to install ubuntu 19.04 and I get the same issue. First I installed steam from the repos, then I uninstalled it and downloaded the deb package from steampowered.com and still get the issue.

Farcrada commented 5 years ago

I run WireGuard at work to tunnel home (wg-quick up xyz), if I turn it off I can instantly and consistently log into Steam. Latest updates of everything (fresh Steam install too). All relevant places to get Steam have the same result; Software Manager, packages (terminal apt install steam) and the .deb on the website.

When reconnecting WireGuard once logged into Steam, downloads aren't working. Steam friends-chat still receives and (seems to) send messages, thus I still appear online. Starting a new install doesn't even start Create local game files...; just hangs.

Linux Mint 19.1 (Cinnamon) Kernel: 4.15.0-52-generic

evcz commented 5 years ago

Seems something similar could be affecting csgo servers (on centos 7) where external http calls using steam libraries seems to be randomly affected too when the payload is big resulting in fragmented packets

blastermaster77 commented 5 years ago

Just asking, did you fresh install steam or are you using a previous installation? The problem manifests when you delete all steam installation with the newest kernel with the tcp stack security update.

On Fri, Jun 21, 2019, 4:03 PM dearlygparted notifications@github.com wrote:

I haven't had any issues connected to Steam, and I've been upgrading my kernel regularly. Currently running this kernel:

$ uname -r 5.1.12-arch1-1-ARCH

What am I missing?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/steam-for-linux/issues/6326?email_source=notifications&email_token=ACHAHPXGZFQVYIJT7FBRZ6DP3UXZ5A5CNFSM4HZOAO32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYJOTIQ#issuecomment-504555938, or mute the thread https://github.com/notifications/unsubscribe-auth/ACHAHPQF2P5VQRRQ6DDFPW3P3UXZ5ANCNFSM4HZOAO3Q .

jtfen86 commented 5 years ago

Running Arch with 5.1.12-zen1-1-zen and Steam through LSI ("Use native runtime" disabled because Steam webhelper bug). No connection issues here.