-
Notifications
You must be signed in to change notification settings - Fork 174
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 crashes when WPA3 is used #7832
Comments
Same here, changing the WiFi back to WPA2 is a workaround. Up until today, Steam worked fine with WPA3. steam -console
|
To be honest, I find it quite disturbing that WPA2 vs WPA3 makes any kind of difference to Steam. How you connect to the network is really none of its business. |
@chewi maybe it has something to do with in-home streaming and device discovery. |
I'm seeing the exact issue after update yesterday. |
I'm seeing the same thing on two of my PopOs systems, everything else in the house steam is fine, and yes both systems have WIFI6 cards. Everything was fine until today. Hopefully they push out a rollback until they figure out what part of the update caused this. I see the exact same error above when I run steam in terminal. |
Since yesterday, I have the same issue on Fedora 34 with an Intel AX200 Wifi 6 card. This is on the non-beta release. Like for everyone else, switching to WPA2 makes Steam launch normally again. |
Is this crash happening with or without a 32-bit If an up-to-date 32-bit (I suspect this might be an incompatibility between the older |
I think it's keeping track of this information because when it runs in SteamOS mode as an "appliance"-style UI ( One way to avoid issues like this would be to avoid entering that code path when not in SteamOS mode, but I think the same code is currently used to determine whether you have network connectivity at all, so that it can go into offline mode if you don't. Ideally it would be using netlink ( |
Thanks, Simon, I had similar thoughts myself after posting that and I like your suggestion. I was aware that it interfaced with NetworkManager before and I always assumed that was just to check whether you were online or not. It's not effective on my system as I don't use NetworkManager but I still have it installed to satisfy the dependency. I haven't hit this issue myself but a root password prompt from PolicyKit regarding NetworkManager has started appearing on my daughter's OpenSUSE system. I've worked around it for now but I should file an issue here. It may be related to this issue. |
For people who are experiencing this crash, another piece of information that would be useful is: if you look at the WPA3 network's configuration in For WPA2 it's typically |
Installing |
Thanks, that's consistent with what I thought the root cause might be. It looks like the older |
@smcv Thanks! |
The underlying libnm bug is fixed in https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/887, and a backport into the Steam Runtime is in progress. |
Steam beta client has been updated with the fix and should no longer be crashing (June 11th). Please retest. |
@TTimo I can confirm that without |
I just upgraded my system to Wifi 6 and encountered this problem. I'm on Ubuntu 21.04 and using an Intel AX210 wifi card. I can confirm that the following command has fixed my issue, Steam now opens and I can play games no problem:
I can also confirm that the WPA3 is in use:
I am not using the beta, so I'm not sure if this is fixed already, but I thought I would post just in case. Thanks. |
Just opted in to the beta, which works for me when the regular version required me to delete my ~/.steam folder every time. |
Thanks, but if you don't have new information, we don't need "me too" reports. The current situation is:
A future update to the general availability branch should pick up the same fix that's in the beta.
That sounds like a different bug, probably #7813 (which is also present in the general availability branch but fixed in the beta branch, and is not avoided by installing a 32-bit libnm). If that is the bug you are experiencing, a less destructive workaround for the general availability branch is to configure Steam to stop remembering your password (#7813 (comment)). |
The bug still has the "Need Retest" label, so I confirmed the bug is gone in the beta. |
If you like to apply the workaround on Fedora 34, you need to install the "NetworkManager-libnm.i686" package.
|
Per "Fixed crashes when on a WPA3 wireless network" in the 2021-07-13 Steam client update, closing as fixed. |
Please describe your issue in as much detail as possible:
Steam crashes on startup with
libnm:ERROR:libnm-core/nm-setting-wireless-security.c:837:need_secrets: code should not be reached
when a WPA3 Wi-Fi network is configured.This happened to me on more than one machine (Arch with KDE Plasma and Pop OS with GNOME).
I use an Intel Wi-Fi 6 AX200.
Steps for reproducing this issue:
libnm:ERROR:libnm-core/nm-setting-wireless-security.c:837:need_secrets: code should not be reached
Workaround
I got steam starting again by manually changing all Wi-Fi networks back to WPA2. This worked also on Pop OS.
The text was updated successfully, but these errors were encountered: