20.10: WIFI will not reconnect automatically. #1490
Comments
|
I can report that I have the same issue. And it is a little more concerning - the wifi at my main place of work drops out for two minutes or so every few hours. So, when the wifi returns, PopOS does not reconnect to the wifi automatically. Every other operating system I have does reconnect automatically. Therefore, PopOS becomes virtually unusable if I want to have services running in the background while I'm away from the machine. |
|
I posted on PopOS subreddit and I didn't get many responses. I am able to reproduce it with different hardware, so I thought for sure it would be affecting more people. |
|
@ZeddieXX just tested with mine and it reconnected! One thing that I changed on my pop install is I switched from the default network backend (networkd) to NetworkManager (because I handles wireguard routes from netplan config more intuitively). You can google around how to make the switch, but from my recollection, I had to:
To see if you're running NetworkManager already or to verify the switch: |
|
@ZeddieXX perhaps a safer way to test my hypothesis is to boot into a pop os recovery/live usb which is 20.04 and uses NetworkManager as network backend. Boot into that, connect to the wi-fi and see if it's improved. If it is, then consider booting back into 20.10 and trying to switch over permanently. |
|
@curiousercreative Thanks. I followed your steps to disable networkd and enable NetworkManager, but still having the same issue. That was a good observation though. I didn't know Pop!_OS 20.10 used networkd instead of NetworkManager. I use NetworkManager in Arch, so that was a possible solution. |
|
@curiousercreative Since switching to NetworkManager didn't help, I just switched back to systemd-networkd. Now I don't see any NICs (wired or wireless). Gnome Settings says NetworkManager needs to be running. Maybe it was running NetworkManager the entire time? I'll be switching back to NetworkManager. |
|
@ZeddieXX that's a bummer, sorry to hear. I don't know exactly what to recommend other than to seek help on the pop os chat |
|
Same issue here. I need to manually reconnect after a wifi dropout even though the connection is marked as "connect automatically". I am on a Gazelle (gaze14) so do not expect a hardware issue. NAME="Pop!_OS" All the online help I can find is for the case where it won't connect at all. In my case, connection happens automatically at boot as expected, but it just does not reconnect if the wifi signal drops out and returns |
|
After not seeing any activity here from any devs who can reproduce the issue, I am thinking about moving to a different distro. |
|
@ZeddieXX did you already confirm via live boot with another distro that it's improved? I'd try with Ubuntu (maybe it's an upstream issue?) and something else. I just tested mine again and it reconnected immediately. It could also be network related? Does your network have multiple access points with the same SSID for example? I have just the one AP. |
|
I haven't tracked it down - it is only a minor bother in my workflow. I'm not sure where the issue is. I mostly use gnome and the gui doesn't let you get to the same network settings as in Cinnamon so I may have something odd set. I have cinnamon as a backup DE and when I get a chance will test it out |
I haven't tried a live Ubuntu, but will check it out now (downloading 20.10). As for the SSID and APs, it happens at home (single WIFI router), 2 cellular hotspots (my phone, and my co-worker's phone), as well as my company's WIFI (AeroHive - 3 near me, same SSID of course - suppose to allow roaming). ALL of them behave the same. However, I'm now on vanilla Arch now (still fine tuning the install) and it works great. It just reconnects without issues (on Gnome). Downloading Ubuntu Live 20.10 now, so stay tuned. EDIT: It is working just fine in Ubuntu Live 20.10. This issue of reconnecting automatically to WIFI seems to only be on Pop!_OS 20.10. I haven't tried 20.04 yet though. |
|
FYI, also tried this on a Pop!_OS 20.10 live usb, and the behavior is the same. |
|
Adding this update: I have a ticket open with System76 since I had a GALP5 with Pop!_OS installed. Aaron: ZeddieXX: This behavior isn't limited to a degrading WIFI signal. It also happens when there is a strong solid connection, then I turn off the hotspot. Later, when I turn it back on while still within range, it will NOT reconnect. |
|
I'm able to recreate this by turning a phone hotspot off and back on; however, I am also seeing the same behavior in a live disk of Ubuntu 20.10. The network reconnects the first time I turn the hotspot off and back on, but after that, it usually doesn't reconnect. (If I make a change to the configuration, such as saving a MAC address to the connection profile, it will reconnect a couple of times, then go back to not reconnecting.) @ZeddieXX When you tested in Ubuntu 20.10 and saw different behavior than I'm seeing, how many times did you disconnect/reconnect? Are you waiting until the WiFi icon in the top-right menu goes away and the |
|
Since you mentioned it was also working correctly in Arch, I tried a newer version of NetworkManager. (Ubuntu is currently shipping version 1.26.2, while Arch is shipping version 1.30.2.) Reconnection seems to be much more reliable with NetworkManager 1.30; I downloaded and installed the Debian Sid packages, but Ubuntu 21.04 (Hirsute) also has version 1.30 already. If you'd like to test this out, download these eight Debian Sid .deb files: https://packages.debian.org/sid/amd64/network-manager/download Then install them using these commands: Then reboot. After that, do your networks reconnect the way you're expecting? (If so, I would recommend waiting until Ubuntu/Pop 21.04 are released later next month with the newer NetworkManager version.) |
Honestly, I just leave with the hotspot for about 5 minutes then come back. I noticed if I turn it off, then see the WiFi indicator on Gnome go away (shows disconnected), then turn it back on within a few seconds, it will reconnect just fine. It's only after a few minutes of disconnection that seem to cause it to not reconnect when the hotspot comes back on. Since I am now on Arch on my GALP5, I'm using a different laptop to troubleshoot this with you. I'm on the HP zBook 15u G6. When I have some time, I will cat the log for you and post it here. |
When I get some time, I'll give this a try and report back. I would LOVE to get back on Pop!_OS because I'm having issues with Arch not shutting down the GALP5 and I haven't had the time to troubleshoot it. Other than this WIFI issue, I like using Pop!_OS as my main distro. |
|
Here's the output dpkg: error processing archive ./network-manager_1.30.0-1_amd64.deb (--install): dpkg: error processing package libnm0:amd64 (--install): dpkg: error processing package network-manager-pptp-gnome (--install): dpkg: error processing package network-manager-pptp (--install): dpkg: error processing package ppp (--install): dpkg: error processing package pptp-linux (--install): |
|
@ZeddieXX First, it looks like you have Same thing for libnettle8: https://packages.debian.org/sid/i386/libnettle8/download Second, you may need to change the order of packages and/or run the command more than once until all of them install and configure. If I recall, I ran it with |
I got it installed now by using these two lines: sudo dpkg -i ./network-manager_1.30.0-1_amd64.deb ./libgnutls30_3.7.1-1_amd64.deb ./libnm0_1.30.0-1_amd64.deb ./libnettle8_3.7-2.1_amd64.deb ./network-manager-pptp-gnome_1.2.8-3+b2_amd64.deb ./network-manager-pptp_1.2.8-3+b2_amd64.deb ./pptp-linux_1.10.0-1_amd64.deb ./ppp_2.4.9-1+1_amd64.deb ./libgnutls30_3.7.1-1_i386.deb ./libnettle8_3.7-2.1_i386.deb I wonder if I needed the 32-bit packages because I also have Steam/Proton/Lutris installed. I believe they require some 32-bit library for some games. Just rebooted as well, and tested: First test, it worked! It looks like it reconnected after I left with my HotSpot. I'll didn't leave for as long as I normally do. I'll leave the hotspot off or disconnected for a longer time and report back. Update: It's working now! So is it a bug with the Network Manager version that's included in Ubuntu/Pop!OS? Would you push a new version of Network Manager to Pop!OS 20.04 and 20.10? UPDATE: Now that I know what to look for, I found this: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1565717 |
|
Glad to hear the newer NetworkManager solves the issue!
That would be my guess as well. You could tell for sure by installing aptitude and running
We're not currently shipping NetworkManager ourselves, it's coming from Ubuntu (you can see this with Like I said, the working version you're running now (1.30.0) will be included by default with Ubuntu/Pop 21.04. I just tested on a 20.04 machine (with NM 1.22.10), and it reconnected ten times in a row (which didn't happen on the 20.10 machine with NM 1.26.2), so this issue doesn't appear to affect that version. |
jacobgkau
changed the title
|
Good to know @jacobgkau . For now the workaround you gave me works on 2 of my Pop!_OS machines running 20.10. I hope to upgrade to 21.04 soon! |
Distribution (run
cat /etc/os-release):NAME="Pop!_OS"
VERSION="20.10"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.10"
VERSION_ID="20.10"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=groovy
UBUNTU_CODENAME=groovy
LOGO=distributor-logo-pop-os
Related Application and/or Package Version (run
apt policy $PACKAGE NAME):N/A
Issue/Bug Description:
When laptop moves too far from WIFI AP or portable WIFI hotspot moves too far, Pop!_OS 20.10 will disconnect. When laptop or hotspot moves within range, the WIFI does not reconnect as expected. This happens with other laptops, so it is not a hardware specific issue. The make/models of laptops I have tried this on:
System76 Galago Pro (GALP5) - Intel WIFI AX-201
HP zBook 15u G6 - Intel WIFI AX-200
HP EliteBook 840 G3 - Intel WIFI 8260 (rev 3a)
Dell Latitude E7450 - Intel WIFI 7265 (rev 59)
HP z400 (desktop) - Unknown USB Realtek-based WIFI (2.4 GHz only)
This happens on both the 2.4GHz and 5GHz bands, so it doesn't matter which one. "Connect automatically" is enabled.
Steps to reproduce (if you know):
Expected behavior:
Pop!_OS should reconnect to the WIFI signal as soon as it is within range.
Other Notes:
Connect automatically is enabled. Doesn't matter the SSID name, 2.4 GHz, or 5 GHz. Other OSes on the same hardware reconnects just fine when WIFI signal is back within range.
The text was updated successfully, but these errors were encountered: