Skip to content
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

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

Open
killerrabbit opened this issue Jun 19, 2019 · 106 comments

Comments

Projects
None yet
@killerrabbit
Copy link

commented Jun 19, 2019

Your system information

  • Steam client version (build number or date): Latest, can't determine exact version
  • Distribution (e.g. Ubuntu): Debian 9 Stable
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

@shirona

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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.

@flinterson

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link
Author

commented Jun 20, 2019

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.

@mark-blum

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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.

@hartmunt

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

$ steam -tcp
@dhollinger

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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.

@kisak-valve kisak-valve changed the title Steam does not start on Debian 9 stable Steam does not connect on kernels newer than 2019-06-17 Jun 20, 2019

@XakepSDK

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 20, 2019

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

This comment has been minimized.

Copy link

commented Jun 21, 2019

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

@blastermaster77

This comment has been minimized.

Copy link

commented Jun 21, 2019

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

This comment has been minimized.

Copy link

commented Jun 21, 2019

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

@jonlap

This comment has been minimized.

Copy link

commented Jun 23, 2019

Tested with 5.1.14-arch1-1-ARCH and Steam is now working again. Thanks everyone!

@RedSparr0w

This comment has been minimized.

Copy link

commented Jun 24, 2019

Thanks @DoogeJ, That fixed it for me also 👍

@linuxgameconsortium

This comment has been minimized.

Copy link

commented Jun 26, 2019

@sgtnasty What was the process you used to get the Steam client to work?
CLI? Purge?
Do you have "steam-devices" installed? Or for that matter "steam:i386"?

@Emanem

This comment has been minimized.

Copy link

commented Jun 26, 2019

@sgtnasty What was the process you used to get the Steam client to work?
CLI? Purge?
Do you have "steam-devices" installed? Or for that matter "steam:i386"?

Was able to connect ~3 hours ago, now it's refusing to connect.
Running on Ubuntu 18.04 with HWE kernel: 4.18.0-24-generic

@Emanem

This comment has been minimized.

Copy link

commented Jun 26, 2019

@sgtnasty What was the process you used to get the Steam client to work?
CLI? Purge?
Do you have "steam-devices" installed? Or for that matter "steam:i386"?

Was able to connect ~3 hours ago, now it's refusing to connect.
Running on Ubuntu 18.04 with HWE kernel: 4.18.0-24-generic

Never mind, it worked now after some hours. Looks like the auth servers are overrun with the sale...

@Saroumane

This comment has been minimized.

Copy link

commented Jun 26, 2019

For those not having success with the -tcp flag.

My laptop was running ubuntu 18.04 lts and kernel 4.18.0-22-generic and it ran fine with the flag.
My desktop was running ubuntu 18.04 lts with kernel 4.15 and it did not ran with the flag, so I just updated the kernel to 4.18 with ukuu and now runs fine with the flag.

Not sure if this is the smartest way to do it, but it worked for me.

EDIT:
Just updated both devices to kernel 5.1.14 and works fine without the flag...

If you use nvidia proprietary driver, how do you do after updating to 5.1.1x kernel (installed with DoogeJ link) ?
I tried sudo dkms autoinstall and sudo apt reinstall nvidia-driver-418 in recovery mode without success, I can't boot anymore with 5.1.15 kernel in graphical mode.

@Saroumane

This comment has been minimized.

Copy link

commented Jun 26, 2019

To avoid other people in my case (Ubuntu 19.04 + nvidia proprietary driver 418) wasting time :
List of kernel tried with ubuntu-mainline-kernel.sh script :
v5.0.20 and v5.0.21 => Kernel Panic at boot
v5.1.0 / v5.1.1 / v5.1.12 / v5.1.13 / v5.1.14 / v5.1.15 => can't reinstall nvidia driver. (The "apt" way does nothing, and sudo dkms -k KernelVersion fails at build)

Now I could try to mess with ppa:graphics-drivers/ppa or official nvidia binary installer, but it usually creates more harm than good.

ENDING SPOILER :
I finally chose to downgrade to kernel 5.0.13. I know I'm losing security fixes, but at least I don't break my system even more.

@fwsGonzo

This comment has been minimized.

Copy link

commented Jun 26, 2019

ENDING SPOILER :
I finally chose to downgrade to kernel 5.0.13. I know I'm losing security fixes, but at least I don't break my system even more.

That's too bad. Guess I will wait, and in the meantime try -tcp at commandline.

@RafneQ

This comment has been minimized.

Copy link

commented Jun 26, 2019

Hi, couple days ago I tried to install and launch Steam on fresh Kbuntu 18.04 and during login to Steam account I got error message "Could not connect to Steam network". At first I thought this was due summer sale :) but Steam was working fine on other devices. Tried on kernels 4.18.0-22 and 4.18.0-24 and in both cases Steam was not able to connect to my account.

Unfortunately doing reset or starting with "-tcp" didn't help. The only thing that worked in my case was downgrading kernel to 4.18.0-21. After that everything is fine.

@kisak-valve

This comment has been minimized.

Copy link
Member

commented Jun 27, 2019

Good day folks, thanks to those involved in triaging this issue.

The fix for this issue has landed in 5.1.14, 4.19.55, 4.14.131, 4.9.184, and 4.4.184. The issue is understood and there's nothing more to investigate on this issue report. Additional confirmations here won't expedite the fix landing in distro-maintained kernel releases.

While the Steam client is affected by this issue, the fix is not considered a critical security fix, so please give the various package maintainers some time to pick this up in their normal update cycle before giving them a friendly reminder.

@Kurgol

This comment has been minimized.

Copy link

commented Jun 28, 2019

This is hugely annoying because on my asus n56vm laptop running ubuntu 19.04 I get the same problems described above (and it's now kernel 5.0.0-19 so above the fix level).
image

But on my xps 13 running the same distribution and kernel, on the same wifi network - the xps works fine.

I have tried completely purging and re-installing steam on the asus, including removing the .steam folder after purging.

Neither of my machines are participating in the steam beta.

edit: turns out the xps13 was actually running 5.0.0.20. Now I have upgraded the n56vm to the same kernel that's working too, so I think there is a regression in 5.0.0.19.

@ldra02

This comment has been minimized.

Copy link

commented Jun 28, 2019

Your system information

* Steam client version (build number or date): Latest, can't determine exact version

* Distribution (e.g. Ubuntu): Debian 9 Stable

* Opted into Steam client beta?: No

* Have you checked for system updates?: Yes

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

System Info:

Steam Client Version: https://imagebin.ca/v/4m9MeDy7Vflo (screen shot)
Kernel Version: 4.15.0-54-generic
Distro: Ubuntu 64b 18.04

Fresh install, installed pulse, steam, UFW (allowed pass all as a troubleshooting step, hoping it would open ports)

AMD hardware (idk if this makes a difference)

Initially was running 4.x.x.x some other kernel, newer, downgraded, and worked after that.

Opted into the latest Proton.

Again, I am able to connect with this config. Booted in term with -tcp flag. Will test without.

@ugly95

This comment has been minimized.

Copy link

commented Jun 28, 2019

The fix for this issue has landed in 5.1.14, 4.19.55, 4.14.131, 4.9.184, and 4.4.184. The issue is understood and there's nothing more to investigate on this issue report. Additional confirmations here won't expedite the fix landing in distro-maintained kernel releases.

I can confirm that this is also fixed in 5.0.0-20 on Linux Mint.

@pete-h

This comment has been minimized.

Copy link

commented Jun 28, 2019

Fixed in Ubuntu 18.04 with Kernel 4.15.0-54-generic (64bit)

@linuxgameconsortium

This comment has been minimized.

Copy link

commented Jun 28, 2019

Fixed in Ubuntu 18.04 with Kernel 4.15.0-54-generic (64bit)

Confirmed. As of June 27th.

@FJoeXXL2

This comment has been minimized.

Copy link

commented Jul 1, 2019

4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Problem gone for now, "-tcp" option didn't made any difference before.

@shirona

This comment has been minimized.

Copy link

commented Jul 5, 2019

Running right now kernel 5.1.15 on NixOS unstable. Running Steam in TCP mode has been working ever since 5.1.11, and while the issues in the default UDP mode have been alleviated, it's still not logging in consistently. Whereas in 5.1.11 I had around a <10% chance of connecting in UDP mode, now in 5.1.15 I have around a 40% to 50% chance of logging in.

@NoXPhasma

This comment has been minimized.

Copy link

commented Jul 9, 2019

I'm on 5.1.16 and still unable to log in consistently over UDP.

@dope250

This comment has been minimized.

Copy link

commented Jul 10, 2019

Was on debian 4.9.0-9-amd64 and got the problem. Downgraded to 4.9.0-8-amd64 and it worked again.
-tcp switch didn't worked.

@draeath

This comment has been minimized.

Copy link

commented Jul 11, 2019

openSUSE Leap 15.1 with kernel 4.12.14-lp151.28.7-default also has this problem, -tcp argument doesn't help either.

@nosoop

This comment has been minimized.

Copy link

commented Jul 16, 2019

Also affects SteamCMD on the current version of Debian Buster, package linux-image-4.19.0-5-amd64 (4.19.37-5). Last known good version on Debian is the previous version of linux-image-4.9.0-9-amd64 (4.9.168-1+deb9u2) on Debian Stretch, which can be pulled using the Debian snapshot archive.

@sizeofbool

This comment has been minimized.

Copy link

commented Jul 16, 2019

It looks like some sort of misconfigured anti-DDoS measures on Valve side are preventing Steam Client from connecting properly.
On my Debian 'stretch' system, kernel version is 4.19 and these connectivity problems are happen sporadically when I launch Steam Client. It complains about obviously working Internet connection, and if I restart Steam Client a few times, without changing or doing anything it will work.
It is hard to diagnose on user side because some Valve hosts are not responding to ICMP requests (eg. 162.254.198.132) and you can't tell if this host is working or not.

@cheloide

This comment has been minimized.

Copy link

commented Jul 20, 2019

A workaround for debian (since we won't be getting kernel updates anytime soon) is downloading this kernel image and installing it with dpkg:

wget https://snapshot.debian.org/archive/debian/20190316T031117Z/pool/main/l/linux-signed-amd64/linux-image-4.19.0-4-amd64_4.19.28-2_amd64.deb -o /tmp/linux-image-4.19.0-4-amd64_4.19.28-2_amd64.deb
sudo dpkg -i /tmp/linux-image-4.19.0-4-amd64_4.19.28-2_amd64.deb

I recommend installing the kernel headers first if you have nvidia drivers.

Rebooting and selecting "Advanced options" in Grub menu and boot with the newly installed kernel image
you will be able to login to steam desktop that way.

After that you will be able to open steam when booting with the current kernel.

credits to Laladen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.