WIFI no longer working after update
Page 1 of 1 (8 posts)
Tags:
None
Registered Member 
|
Taken from my openSUSE thread. As the issue appears to be specific to the KDE network manager widget, I'm posting it here too in hopes of finding a solution.
Upon updating and restarting my openSUSE Tumbleweed laptop, Plasma stopped showing WIFI connections in the network manager widget of the system tray. The WIFI checkbox is there and enabled, the network card is definitely recognized... it's just that there are no connections being listed in the panel despite many being available. I don't seem to have the ifconfig command, but even iwconfig is able to see them just fine from the console. I'll need to use my laptop soon so I must fix the connectivity. Any idea why this might be happening and what I should debug next? Thank you. |
|
Registered Member
|
I got a little help to further investigate this on IRC. It appears the NetworkManager service might be itself acting up.
First of all "nmcli dev wifi" does not list any connections. I understand they should appear there, as they currently are on my desktop computer. The output of "sudo systemctl status NetworkManager" is also rather dubious.
I also did a "sudo journalctl -b -t NetworkManager" which I hope will offer further information:
|
|
Registered Member
|
Okay, something is happening: I ran "sudo systemctl restart wpa_supplicant" followed by "sudo systemctl restart NetworkManager.service". This caused all the WIFI connections to appear and the laptop automatically connected successfully to my router. Perhaps this error explains what might be happening?
If I restart the machine, I need to run the commands again to get Wifi running. I did a forced update of the wpa_supplicant package: The connections still didn't work automatically after restarting, but running just "sudo systemctl restart NetworkManager.service" fixes it after I log in. Now to resolve the problem permanently. |
|
Registered Member
|
It seems I managed to find a permanent solution, which was pointed out in the early stages of this issue. Funny enough it was the NetworkManager Wait Online service causing it. Likely because WIFI doesn't activate at boot time, and without a LAN cable plugged in the machine doesn't have early internet connectivity thus the service errors out. I disabled it as a boot time optimization after looking it up and seeing that it's useless, but after restarting I noticed all my connections are immediately working again.
As that service is pointless on my laptop and I have no reason to re-enable it, I can consider the issue resolved in my case. This still isn't normal behavior and will likely cause headaches to other users, so I'm leaving the discussion open for the team to debug it. I'd suggest booting a machine that's not connected to the internet via any connection that can be immediately detected (eg: cable internet) to get a complaint from NetworkManager Wait Online, then seeing if this causes WIFI connections to be missing after you log in. |
Manager
|
Looks like something you should report as a bug, as it seriously hinders the connectivity.
Running Kubuntu 22.10 with Plasma 5.26.3, Frameworks 5.100.0, Qt 5.15.6, kernel 5.19.0-23 on Ryzen 5 4600H, AMD Renoir, X11
FWIW: it's always useful to state the exact Plasma version (+ distribution) when asking questions, makes it easier to help ... |
|
Registered Member
|
I reported it with the openSUSE team for now, hopefully they can look at it soon: https://bugzilla.opensuse.org/show_bug.cgi?id=1144950 |
|
Manager
|
if it is specific to the KDE Network Manager it should be reported upstream here: https://bugs.kde.org
Let's hope the SUSE guys move it upstream if needed 
Running Kubuntu 22.10 with Plasma 5.26.3, Frameworks 5.100.0, Qt 5.15.6, kernel 5.19.0-23 on Ryzen 5 4600H, AMD Renoir, X11
FWIW: it's always useful to state the exact Plasma version (+ distribution) when asking questions, makes it easier to help ... |
Registered Member
|
I had a different problem on Manjaro testing with wireless networks showing but I couldn't connect to mine, even after restarting NetworkManager.service and rebooting the system. (I could connect via ethernet.) What worked after a reboot was restarting wpa_supplicant and then NetworkManager.service.
|
Page 1 of 1 (8 posts)
Bookmarks
Who is online
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]
