WiFi networks list disappears (device type not reloaded)

[Shinjan Saha]

************
💥 WARNING 💥
************
If you are still experiencing this bug please don't comment here, but look at these: (https://goo.gl/LdPpYG)

******************
 HOW TO REPRODUCE
******************
Boot the system.

********
 RESULT
********
From time to time, some of these happen:
- The applet doesn't list any wireless network.
- The applet doesn't show the name of the current network.
- The icon shows the wired connection symbol, instead of the wifi one.

*************
 WORK AROUND
*************
(http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues)

*****
 FIX
*****
The applet needs to re-read the DEVTYPE after the device name changed.

*******************
 HOW TO TEST A FIX
*******************
In the Terminal application enter:
nmcli dev

If it works, in the line for the wireless device, the TYPE column should be "wifi". If it doesn't it will be "ethernet".

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Cip Man (cipman-p)]

Same here.
It does the same if the steps to reproduce (2) + (3) are replaced with suspend/wake up.

[Cip Man (cipman-p)]

Easier workaround:

sudo systemctl restart network-manager.service

[Dragon Ball (dragonballz2k)]

also for me if you go into system settings, and go into network I can you still see the wifi network list.

[Shinjan Saha (sahashinjan)]

Is there any ETA for fixing this bug?

[Cip Man (cipman-p)]

ETA is with the release of Ballsy Baboon (i.e next ubuntu LTS - 18.04) :):)

Try disabling bluetooth if your system has it and you don't need it. Works for my laptop - now wifi works as it should on suspend or enable/disable wifi. If no luck, search askubuntu, there are some scripts that might fix this for your system.

[MBWD (xmbwd)]

This works to reset the wifi temporarily: `sudo systemctl restart network-manager.service`.

The scripts can help fix the wifi resume on suspend issues. However, I have not seen a script that fixes the inability to switch networks on an active wifi connection without it going dead.

Also, on a fresh install, I experienced a fourth problem:

4. Network manager creates a new instance of the network each time it connects to it (e.g., wifi_1; wifi_2; wifi_3. As a result, the user has to input a new password each time.

This bug caused me to roll back to 15.10. Hoping it gets fixed soon.

[bford16 (bford16)]

On my machine, the network connection resumes - if I do [nmcli g], I see that the network is connected. For me, the only issue is that the nm-applet reverts to the Ethernet setting (two arrows), and does not show the list of wireless networks available. Are we really going to have to wait TWO YEARS for a fix?

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1574347

[Shih-Yuan Lee (fourdollars)]

The fix is at https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd4d8b24da29abfc786ce0b3030c74559b93d034.
NetworkManager 1.2.0 in xenial-proposed still has this issue.

[Jane Atkinson (irihapeti)]

I'm still having the issue on my EeePC 900 after installing NetWorkManager 1.2.0 from xenial-proposed.

[hussain (lovalim)]

I m also having the same issue.

[Cip Man (cipman-p)]

1.2.0 version was compiled before the fix mentioned in post #11 was released.
In other words, version 1.2.0 *does not* include the patch presumed to fix this bug.

To double check this, compare NetworkManager-1.2.0/src/platform/nm-linux-platform.c in the source archive https://launchpad.net/ubuntu/+archive/primary/+files/network-manager_1.2.0.orig.tar.xz located at https://launchpad.net/ubuntu/+source/network-manager/1.2.0-0ubuntu0.16.04.1
with the diff from https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd4d8b24da29abfc786ce0b3030c74559b93d034

[hussain (lovalim)]

The network manager version on my laptop is 1.1.93 how can i update it to 1.2?

[Cip Man (cipman-p)]

The recommended method to update packages to proposal versions is described at https://wiki.ubuntu.com/Testing/EnableProposed - note the *selective upgrading*.

[Jane Atkinson (irihapeti)]

@Cip Man:

That explains it, then. I'm happy to wait for the patched version to come through.

My current workaround is to add the line

service NetworkManager restart

to /etc/rc.local

[hussain (lovalim)]

Thanks friends , but i m not that expert with commands in ubuntu. should i wait @jane, will it auto update once the patched version releases and how u installed 1.2 on ur Eeepc

[Jane Atkinson (irihapeti)]

@hussain

I installed 1.2 on my EeePC by enabling the Proposed repository in Software and Updates. This isn't usually recommended for everyone as it can break things, but is useful for testing.

Once the patched version is released and is moved from the Proposed to the regular repository, it will automatically be updated.

[hussain (lovalim)]

@Jane

Thank you for the information. but i dont have proposed repository in software and updates.

[Cip Man (cipman-p)]

The option is in the Developer tab (last on the right), see this image http://i.imgur.com/CdTRGqF.png

[hussain (lovalim)]

@Cip Man

Thank you for the information.

[Marcin Sochacki (wanted)]

So is there some Ubuntu package containing the fix already, so that we could test it?

[Cip Man (cipman-p)]

No package to test yet.
The good news is that a new source, namely 1.2.2, was just released upstream few hours ago: https://download.gnome.org/sources/NetworkManager/1.2/

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Will Cooke (willcooke)]

Added to Trello: https://trello.com/c/LXqaTEnC/1-bug-1574347-wifi-network-list-disappears-from-network-manager-applet

[Adam Conrad (adconrad)]

Hello Shinjan, or anyone else affected,

Accepted network-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network-manager/1.2.0-0ubuntu0.16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Alan Pope 🍺🐧🐱 🦄 (popey)]

That fixes it for me on my T450! Thanks everyone!

[Cip Man (cipman-p)]

It does *not* fix it for me.
On a clean installed Xenial I upgraded from xenial-proposed only the packages related to network-manager. Namely:

$ dpkg -l | grep 1.2.0-0ubuntu0.16.04.2
ii libnm-glib-vpn1:amd64 1.2.0-0ubuntu0.16.04.2
ii libnm-glib4:amd64 1.2.0-0ubuntu0.16.04.2
ii libnm-util2:amd64 1.2.0-0ubuntu0.16.04.2
ii libnm0:amd64 1.2.0-0ubuntu0.16.04.2
ii network-manager 1.2.0-0ubuntu0.16.04.2

No dice. Returning from suspend no networks listed, wired or grayed wifi symbol but the network works.

[Cip Man (cipman-p)]

P.S. Just to be thorough, I also followed the 'Steps to reproduce' stated in the bug description and the results are the same as described in 'Problems'.

[Alan Pope 🍺🐧🐱 🦄 (popey)]

Perhaps you should also have updated network-manager-gnome package which contains the nm-applet.

I updated both network-manager and network-manager-gnome, then restarted both network-manager and nm-applet and now the problem is gone.

[Robert Hooker (sarvatt)]

No luck here either, the indicator is broken after a suspend/resume only showing a wired connection.

ii libnm-glib-vpn1:amd64 1.2.0-0ubuntu0.16.04.2 amd64 network management framework (GLib VPN shared library)
ii libnm-glib4:amd64 1.2.0-0ubuntu0.16.04.2 amd64 network management framework (GLib shared library)
ii libnm-util2:amd64 1.2.0-0ubuntu0.16.04.2 amd64 network management framework (shared library)
ii libnm0:amd64 1.2.0-0ubuntu0.16.04.2 amd64 GObject-based client library for NetworkManager
ii network-manager 1.2.0-0ubuntu0.16.04.2 amd64 network management framework (daemon and userspace tools)
ii libnm-gtk-common 1.2.0-0ubuntu0.16.04.1 all library for wireless and mobile dialogs - common files
ii libnm-gtk0:amd64 1.2.0-0ubuntu0.16.04.1 amd64 library for wireless and mobile dialogs (libnm-glib version)
ii libnma-common 1.2.0-0ubuntu0.16.04.1 all library for wireless and mobile dialogs - common files
ii libnma0:amd64 1.2.0-0ubuntu0.16.04.1 amd64 library for wireless and mobile dialogs (libnm version)
ii network-manager-gnome 1.2.0-0ubuntu0.16.04.1 amd64 network management framework (GNOME frontend)

[Cip Man (cipman-p)]

@Alan: network-manager-gnome was already at the latest version, the one mentioned by Robert above. But I also upgraded to everything xenial-proposed had 30 mins ago (thinking maybe you did that) and still no luck.

But this is how I made this version work for me (@Robert, maybe you'd like to test this?):
a. reboot (just to make sure we all start from the same point - I noticed it matters here)
b. open a terminal and $ sudo systemctl restart NetworkManager.service
c. test wifi off/on and suspend/resume - now NM works perfect for me (didn't test AP off/on as I can't do that now).
This workaround also works if between a. and b. you perfom c. to check if it works (which isn't for me).

[Sebastien Bacher (seb128)]

the issues reported there could be different one, no point trying to make the SRU perfect before landing or it's never going to move to update, if you still have issue with that new version better to open a new bug and use that for debugging

[Marcin Sochacki (wanted)]

For me, the version 1.2.0-0ubuntu0.16.04.2 fixes the issue with wifi not visible after fresh boot. Now it works fine.

[Pinghao Qi (feifeiqph)]

I'm running the newest versions in stable, just upgraded the applet yesterday:
network-manager 1.1.93-0ubuntu4
network-manager-gnome 1.2.0-0ubuntu0.16.04.1
For me, the issue is already fixed somehow, without needing to update to proposed.

[Cip Man (cipman-p)]

@Pinghao Qi, which issue did the stable version fixed for you, as there are several bug reports merged/duplicated/etc here?

[Pinghao Qi (feifeiqph)]

@Cip Man The issue where after disabling and reenabling wifi makes all wifi APs disappear. Mine also does the same when resuming from suspend. After upgrading, both cases above works fine.

[hussain (lovalim)]

i checked for update many times since yesterday no update for network manager. my version for network manager is still, network-manager 1.1.93-0ubuntu4.

[Cip Man (cipman-p)]

My production box is also updated to the current stable versions (mentioned in post #36) but it still has the issues with vanishing network list & wrong indicator symbol when you turn wifi/AP/suspend off/on (and the workaround in post #33 doesn't work).

[Cip Man (cipman-p)]

@hussain Perhaps the server you update from didn't synchronize yet. Either wait a little more or change 'Download from:' to <Main server> in "Software & Updates" (with xenial-proposed enabled, of course).

[Aron Xu (happyaron)]

@cipman-p with the following version the problem should vanish:

network-manager: 1.2.0-0ubuntu0.16.04.2
libnm-*: 1.2.0-0ubuntu0.16.04.2
network-manager-gnome: 1.2.0-0ubuntu0.16.04.1

We should allow this update to be accepted from -proposed to -updates, otherwise more fixes will be slowed down in their way of arriving.

[Cip Man (cipman-p)]

I agree, it should be accepted to -updates. The diff doesn't look as it might break anything anyway.

[Cip Man (cipman-p)]

One more try:
- new clean released xenial 16.04 amd64 install on a spare partition
- set update server to Main
- update & upgrade
- reboot
- enable -proposed
- update & upgrade
- all relevant package versions precisely as in #32 (@Aron Xu: please note that not all libnm-* are 1.2.0-0ubuntu0.16.04.2, namely libnm-gtk-common and libnm-gtk0:amd64 which are 16.04.1)
-reboot

Result: still not working properly after wifi/AP/suspend off/on.
The only improvement is that now I can make it work after a boot/login with a 'sudo systemctl restart NetworkManager.service' as I wrote in #33.
I can upload a movie for non-believers :)

[hussain (lovalim)]

my download server is "main server"

[Shinjan Saha (sahashinjan)]

I have done the testing on Dell Inspiron.

Upgraded all the following packages

network-manager: 1.2.0-0ubuntu0.16.04.2 - found in proposed
libnm-*: 1.2.0-0ubuntu0.16.04.2
network-manager-gnome: 1.2.0-0ubuntu0.16.04.1

Testings done:-

1. Check after AP on/off - Only improvement is I can see the wifi network list. Other two problems persist. That is, in the original bug description, problem#1 is solved, #2 and #3 still persist.

2. Check after suspend/resume - All the 3 problems persist. No improvement noticed.

[MBWD (xmbwd)]

I can confirm that running an Intel 7260, after upgrading the suggested packaged to 1.2.0-0ubuntu0.16.04.1, and my problem persists:

when I am connected to a wifi AP (AP1) and I try to switch to another AP (AP2), the wifi connection dies -- with no list of accessible APs -- and it gives the little right/left arrows that indicate you have no ethernet connection.

I have to admit, the OPs description of the problem is not clear to me, so I am not sure if this is the same bug or a different one.

In all events, for the bug I think this is (can't change wifi networks), the suggested solutions (i.e., install the latest version of network-manager and two others) do NOT solve it.

[Robert Hooker (sarvatt)]

our intel 7260 bug is still broken on nm 1.2 but its not a regression, it happened on previous versions too. hopefully they can fix it :)

[MBWD (xmbwd)]

Thanks Robert, at least now I know (although, at least for me, there is no wifi issue in 15.10). Is there a separate bug for the Intel 7260 series that I should be watching?

Also, small typo above: I upgraded network-manager to 1.2.0-0ubuntu0.16.04.2 and network-manager-gnome to 1.2.0-0ubuntu0.16.04.1.

[Brian Murray (brian-murray)]

Bug 1581371 seems to be a regression caused by this SRU. Please investigate the matter before releasing this update.

[Aron Xu (happyaron)]

The problem of Bug #1581371 lies in networkmanager-qt, for which kubuntu people is trying to handle their symbol mismatch problem.

[Leopoldo Pena (leopenausa)]

No wifi after resume from sleep is also present in my computer, System 76 Galago Pro. Network manager applet switches to wired connection and no wifi is shown. Log out/in doesn't fix this and reboot is necessary.

[Marcin Sochacki (wanted)]

@leopenausa: have you tried restarting NM instead of rebooting?
sudo systemctl restart network-manager.service

[Launchpad Janitor (janitor)]

This bug was fixed in the package network-manager - 1.2.2-0ubuntu1

---------------
network-manager (1.2.2-0ubuntu1) yakkety; urgency=medium

  * Rebase to upstream stable point release. (LP: #1574347)
  * Use gbp-pq to manage patches.
  * d/rules: Allow parallel building of the package.

 -- Aron Xu <email address hidden> Fri, 13 May 2016 06:40:53 +0000

[Amr Ibrahim (amribrahim1987)]

Bug 1581371 is not a regression according to this comment https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726/comments/19

[Ubuntu Foundations Team Bug Bot (crichton)]

As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of network-manager from xenial-proposed was performed and bug 1584276 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed" tag from this bug report and add the tag "bot-stop-nagging" to bug 1584276 (not this bug). Thanks!

[Sebastien Bacher (seb128)]

the new bug is not a regression from the SRU, setting back to verification-done

[Amr Ibrahim (amribrahim1987)]

Please set back to Fix Committed in Xenial. It's still in -proposed.

[Thierry Carrez (ttx)]

Confirmed 1.2.0-0ubuntu0.16.04.2 fixes the issue that no wifi networks are listed after boot.

[Jane Atkinson (irihapeti)]

Is now working as expected on my EeePC 900. That includes waking from suspend. (I don't use hibernate.)

[hussain (lovalim)]

hey guys i m still have the same issue

[Launchpad Janitor (janitor)]

This bug was fixed in the package network-manager - 1.2.0-0ubuntu0.16.04.2

---------------
network-manager (1.2.0-0ubuntu0.16.04.2) xenial; urgency=medium

  * debian/patches: lp1574347-re-read-link-type-if-the-name-changed.diff
    - Fix Wi-Fi network list disappearing problem (LP: #1574347)

 -- Aron Xu <email address hidden> Thu, 12 May 2016 14:48:57 +0800

[Martin Pitt (pitti)]

The verification of the Stable Release Update for network-manager has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Cip Man (cipman-p)]

This bug is *NOT* fixed!!!
I just upgraded my production machine to 1.2.0-0ubuntu0.16.04.2 from -updates and I have the same issues (as I reported nearly 3 weeks ago in #44 on a test machine): no wifi networks after wifi Off/On, wired symbol etc.

As I already said, what's NEW with 1.2.0-0ubuntu0.16.04.2 is that a manual 'sudo systemctl restart NetworkManager.service' fixes things until next login/boot.

Could it be hardware related? I also have a Dell (Vostro) as @sahashinjan reported in #46 - which was a no go as well.

[Mathieu Trudel-Lapierre (cyphermox)]

Cip Man, you're seeing a different issue with the wireless device. This isn't the same bug.

What gets fixed here is that wireless devices may be seen as *ethernet* rather than wireless, because of confusion in NM in detecting the device type -- it doesn't mean you definitely would have a list of wireless networks if the wireless device doesn't do the scanning properly.

The correct way to verify this bug here is to use 'nmcli dev' and to see whether a device that is supposed to be a wireless device is being listed as "ethernet".

Ideally, please file your own, separate bug so we can fix that as well.

[Cip Man (cipman-p)]

Actually, this bug, WAS a different issue until you (plus Aron Xu and others) changed the title, description, [wrongly] marked this and other bugs as duplicate, changed the testcase, you name it. Look at the original description in the activity log of this bug at 2016-05-12 08:41:52 change.

File my own bug?! I was the 1st to confirm this bug the same day OP filed it 5 weeks ago, look at #3. What would I do it again for?!

Practically, this is now a bug that was "fixed" to match a released NM version.

[Hansen (moteprime)]

I have been following this bug and i'm a bit confused now.
Wasn't it WiFi icon in nm-applet disappear when returning from suspend?
This has not been fis in todays updates.

[Giovanni Mellini (merlos)]

Same problem form me after the updates.
When resuming from suspend I have ad "inactive" icon for wifi/wired connections and I cannot select network profiles (wireless or wired) while connection is ok.
My workaroud is to restart network-manager service in this case but is really annoying.
Giovanni

[Hansen (moteprime)]

I get the up/down arrows in network manager applet
My workaround is to "killall nm-applet" and start nm-applet again.

[Henry J. Douglas (cyberdoug42-deactivatedaccount)]

Same as Hansen, plus connection drops from time to time despite having a "connected state" (clicking my wireless SSID on the applet menu resumes the connection). When the up/down arrows appear, only a reboot is able to fix it. I have been seeing improvements with these last updates, except the very last one, which induced the up/down arrows again and made the connection drops more frequent.

Intel Wireless 3160 - Ubuntu 16.04 (clean install, all updates installed).

[hussain (lovalim)]

Yes Cip you are correct, this bug original form on this thread got keep changing. but Ubuntu support team i recommend as this bug is still not fixed, dont close this thread, as many other have also reported the same.

you guys merged three different bug with one.

[rjb (ron-buehler)]

I do have the same problem as many other's here.
After suspend there's no wifi icon anymore, but the cable network icon with the two arrows. Also it doesn't show the wifi networks anymore.

My lspci output (on Ubuntu 16.04 clean install):
07:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73)
0f:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
 Subsystem: Hewlett-Packard Company RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [103c:1968]

[Hansen (moteprime)]

If 'Ubuntu Stable Release Updates Team' have unsubscribed from the bug shouldn't we make a new bug and ll mark is as 'affecting me'. I think it's the quickest way. Reopening a bug a bothersome.
??

[Christian Heitjan (heitjan)]

I installed the latest updates, but I still have the same problem as others wrote before. After suspend the network icon only shows two arrows and no list of available Wifi networks are shown.

Is there a way to reactivate this bug-report as "doesn't fix" or so?

[Hansen (moteprime)]

I'm not a specialist in these procedures, but it's easy enough to change the status of the bug, the problem are getting the attention of the proper people. In my experience it's not easy getting them back when the have left already.
I think the best way are if we make a new bug, have have as many people as possible to subscribe to it at possible.
A key part are to report it right.

[Aron Xu (happyaron)]

Please open another report if there is other (probably looks the same) issues because this update has released which indeed fixes the problem in current description, but there might be other bugs that may result into similar behavior.

[Hansen (moteprime)]

Could someone with a bit of technical insight open a new bug please.

[hussain (lovalim)]

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401

opened a new case

[gwarah (lhmp1967)]

I've installed 16.04 few hours ago and got the same issue. Seemed solved with these steps (in a terminal) :

$~ sudo apt-get update && sudo apt-get dist-upgrade

$~ $ killall nm-applet && nm-applet &

Reboot after to check if its ok.

[RickB (rick-777)]

This bug affects my Dell Precision (new model 2016).

My workaround is `nmcli con up wifi-sid` in a terminal.

[BR451 (br451)]

network manager 1.2.0-0ubuntu0.16.04.2

Same problem with a fresh computer start.

sudo systemctl restart network-manager.service
-> fix the problem (close wifi, close network, sleep mode, no more bug in wifi list and icon), but it come back after a restart of the computer.

Maybe not a bug from network manager 1.2.0-0ubuntu0.16.04.2 ???

network-manager-gnome 1.2.0-0ubuntu0.16.04.3 is on my computer too

Any idea ? Want more informations ?

[Tumbler (zimbler)]

@BR451 works for me after updating to 1.2.0-0ubuntu0.16.04.3 and restarting network manager.

[Cno (cno)]

FYI: From what I experienced, there is a complex of (probably related) problems.
 NB: I'm applying Ubuntu updates continuously.

Somewhere a year ago, I started experiencing a problem when moving in my house, when apparently another access/antenna of the router was picked. Suspend/wake up was not necessary to have that problem: wifi crashed and no relief of networkmanager restart.
The problem in also showed when I was using my smartphone as hotspot.
In other locations, it happened rather seldom.

Now some time after the 16.04 the problem changed: the provious bug disappeared; the bug described here poped up. Which is less annoying, since there are work arounds.

[lauricat (lauricat)]

I have doing a fair bit of my own testing with this bug - whether this assists or not with a fix not sure, but here are my obseravtions.

Lenevo x220, latest iwlwifi driver [18.168.6.1], Ubuntu 16.04.1 (clean install), latest stable kernel 4.6.5, and latest Network manager 1.2.2-0ubuntu6.

I can report the following:

After Suspend then resume, fault still occurs. Also see nmcli below, output of Nm icon is the 2 vertical arrows (not the wifi symbol) and NO WIFI NETWORKS LISTED - but connected to wifi:

xxx@xxx-ThinkPad-X220:~$ nmcli dev
DEVICE TYPE STATE CONNECTION
wlp3s0 wifi connected Lxxxx 1
enp0s25 ethernet unavailable --
lo loopback unmanaged --

HTH

Cheers...
xxx@xxx-ThinkPad-X220:~$

[lauricat (lauricat)]

More..

Subsequent to installing 16.04.1, I tried a clean install of 16.10 Yaketty Yak. Alpha 1

Only 5 days of testing, but many suspend-resume cycles over the course of a normal work day.

I can report that the problem appeared to not appear with this config!

I had to then subsequently go back to 16.04.1, as the Alpha 1 build was too unstable for my usage.

HTH

Cheers

[suzy (suzy-223)]

I am on 16.04.1, and I too am having this issue. Whenever my laptop (W520) goes into Suspend or Hibernate mode and I boot it back up, the WiFi icon displays the "disconnected" message briefly, and then reconnects--only to display the up and down arrows associated with the Ethernet icon and the Ethernet drop-down menu in the top panel. No SSIDs are shown, and the menu asks me to connect to a WiFi network even though I'm already connected to one.

I have Thinkpad 11 bgn WiFi. Ubuntu displays it as "Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01)". Device name is wlp3s0 rather than wlan0.

[John M (takenreality)]

Same here Lenovo T530 Intel 6205 wifi adapter.
The work around (sudo systemctl restart network-manager.service) works for me most of the time. Sometimes my machine needs a reboot then a router reboot to reconnect. It's an old router but didn't present any issues before Ubuntu 16LTS install. Hopefully coincidental. Good luck!

[Viktor (clicman)]

ubuntu 16.04.1
dpkg -l network-manager*|grep ii
ii network-manager 1.2.0-0ubuntu0.16.04.3 amd64 network management framework (daemon and userspace tools)
ii network-manager-gnome 1.2.0-0ubuntu0.16.04.3 amd64 network management framework (GNOME frontend)
ii network-manager-pptp 1.1.93-1ubuntu1 amd64 network management framework (PPTP plugin core)
ii network-manager-pptp-gnome 1.1.93-1ubuntu1 amd64 network management framework (PPTP plugin GNOME GUI)

Bug still exists.
Lenovo x220
lspci|grep Ne
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)

[Peter Amaral (amaralpeter)]

Please reopen this defect and mark In Progress or other appropriate status. This bug still affects me on Ubuntu 16.04.1, all latest updates applied. The fix released does not work.

$ lspci | grep Ne
09:02.0 Network controller: Ralink corp. RT2561/RT61 rev B 802.11g

I also lose connectivity intermittently after restarting NetworkManager. Please let us know what information we can provide that will help resolve this defect, it is extremely frustrating and significantly breaks the user's experience in Ubuntu.

[Hans-Christoph Steiner (eighthave)]

I am pretty sure I'm having this problem on a Toshiba Chromebook 2 (CB35-B3340) running 16.04 fully updated as of this week. I get the ethernet up/down arrows, there is no ethernet on this laptop. I also get the state where it is disconnected and not showing any wifi networks. It seems to be related to suspend/wake, but doesn't always happen.

$ lspci |grep -i net
01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

ii network-manager 1.2.0-0ubuntu0.16.04.3 amd64
ii network-manager-gnome 1.2.0-0ubuntu0.16.04.3 amd64
ii network-manager-pptp 1.1.93-1ubuntu1 amd64
ii network-manager-pptp-gnome 1.1.93-1ubuntu1 amd64

Running this got things back to normal:
$ sudo service network-manager restart

This looked noteworthy:

# dmesg |grep iwl
[ 10.658028] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7260-17.ucode failed with error -2
[ 11.064468] iwlwifi 0000:01:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm
[ 11.545992] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144
[ 11.546081] iwlwifi 0000:01:00.0: L1 Enabled - LTR Disabled
[ 11.546326] iwlwifi 0000:01:00.0: L1 Enabled - LTR Disabled
[ 11.771068] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 11.777060] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0
[ 12.285642] iwlwifi 0000:01:00.0: L1 Enabled - LTR Disabled
[ 12.285883] iwlwifi 0000:01:00.0: L1 Enabled - LTR Disabled
[ 12.491349] iwlwifi 0000:01:00.0: L1 Enabled - LTR Disabled
[ 12.491592] iwlwifi 0000:01:00.0: L1 Enabled - LTR Disabled
[ 461.381354] iwlwifi 0000:01:00.0: L1 Enabled - LTR Disabled
[ 461.381596] iwlwifi 0000:01:00.0: L1 Enabled - LTR Disabled

[armageddon08 (sayak90)]

I can confirm that this problem still exists on my Acer V5-573G.

[Christian Dysthe (christian-dysthe)]

I am having this problem but in addition nm-applet is often gone from the notifications when my laptop wakes from suspend. I wonder if that is related. I fix it by doing a "killall nm-applet; nohup nm-applet &" but I would rather not have to.

[Gaël Rousseau (rodney78310)]

It happens on my Dell Latitude E6430 after I shut down then restart the wifi with the physical switch. Never happened if I shutdown the wifi from the GUI.

This bug is not resolved from my point of view.

[Gaël Rousseau (rodney78310)]

Result from the test:

GUI: Enable wifi (normal behaviour)
GUI: Enable network (blank wifi icon, then if I restart I have the ethernet icon)
Physical switch (blank wifi icon, then ethernet icon).

[mattebuntu (mattebuntu-deactivatedaccount-deactivatedaccount)]

This bug also affects my Toshiba Satellite C645 with a Qualcomm Atheros WiFi card and happens even if the connection is lost abruptly, like when there is a power outage and both the modem and the router shut down.

[Yiyao Yu (py-tek)]

Still happening on Dell XPS 14 l421x with Intel Corporation Centrino Advanced-N 6235 (rev 24). Already running network-manager 1.2.0. It seems that the network manager applet wifi icon changes back to the ethernet icon every time the system wakes from sleep.

[Yiyao Yu (py-tek)]

More info:
network-manger version: 1.2.0-0ubuntu0.16.04.3
Caused by:
Disabling/Enabling Network via GUI (Blank icon)
Sleep/Hibernate (Ethernet icon)

[Stole Kotev (stolekotev)]

I've been trying to fix this network-manager problem for quite some time and guess what. In the it turned out that it isn't a network manager or ubuntu problem at all. It's a 4.4 kernel issue. Just change the kernel. I manually downloaded and installed kernel 4.6, and ... the problem is gone

[Brian Murray (brian-murray)]

Could somebody on the desktop team please follow up with this bug?

[Aron Xu (happyaron)]

@Brian, I believe the patch should fix mentioned bug, feedbacks shouldn't be the same issue, perhaps another one not addressed yet or kernel issue.

[lauricat (lauricat)]

I can report I'm running 16.04.1, AND the latest stable kernel 4.7.4.

Same problem exists.

x220, Intel 6205 wifi.

Surely Ubuntu must be aware of this massive problem?

...
~L

[Michael J. Ford (finlstrm)]

Same issue here.

Linux voyager 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
02:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]

I also installed the lastest 4.7.x kernel, issue persists...

This is UNACCEPTABLE for an LTS release...

[Dea1993 (andrea-deangelis93)]

same issue, on Ubuntu 16.04.1 64bit, and also ubuntu 16.10 beta 2 (updated).

please solve the issue.

[Mathieu Trudel-Lapierre (cyphermox)]

If you're seeing the wrong icon in nm-applet, please file *YOUR OWN* new bug report, and write the number here. Me-too's distract developers from being able to understand what the problem is, because many people have slightly different issues that all look similar.

As we understand it, the original bug is fixed, where wireless would be detected as wired on boot. That means it would show the arrows icon, but my other issues can lead to the icon being wrong.

Unless you run 'nmcli dev' and see that the wireless device says "ethernet" beside its name, then you are not seeing this here bug and should open a new bug report.

If you run 'nmcli dev', and you have wireless that is connected, but also wired or some other network device connected and you see the arrows, then it *might* be expected behavior. Wired networks always take precedence over wireless if both are connected. If you still think it's wrong, please file a new bug, and include the output of 'nmcli dev' and 'ip route'.

[Antonin Chambolle (antonin-chambolle)]

Ubuntu 16.04 on dell E6430, after upgrade:

- after suspend/resume sometimes the network manager cannot connect (but it tries: it keeps associating/de-associating) [before upgrade, the wifi was broken at this stage, cf below]
dmesg:
[101381.710749] wlan0: authenticate with 42:01:40:59:9f:3c
[101381.712600] wlan0: send auth to 42:01:40:59:9f:3c (try 1/3)
[101381.714512] wlan0: authenticated
[101381.716173] wlan0: associate with 42:01:40:59:9f:3c (try 1/3)
[101381.726242] wlan0: RX AssocResp from 42:01:40:59:9f:3c (capab=0x411 status=0 aid=4)
[101381.728513] wlan0: associated
[101388.076989] wlan0: deauthenticated from 42:01:40:59:9f:3c (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
[101388.104508] cfg80211: World regulatory domain updated:
[101388.104511] cfg80211: DFS Master region: unset
[101388.104512] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)

- if I deactivate and then reactivate the wifi, then it reverts to the old bug (where there is only one network available and nothing happens). sudo service network-manager restart repairs everything...
The bug is still at this point:
[101418.822530] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[101418.869145] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[101423.443499] e1000e: eth0 NIC Link is Down
[101426.202627] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[101426.202873] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[101426.210391] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[101426.210491] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[101426.434605] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[101426.442165] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[101426.442267] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
a problem with the /dev/something, no?

strange...
hope this can be repaired soon. But also in the 14.04 distrib it was sometimes necessary to deactivate/restart the network manager to catch back the signal after resume...
good luck, thanks

[Dea1993 (andrea-deangelis93)]

now i'm using ubuntu 16.10 with proposed updates enabled.
Network-Manager is at version 1.2.4-0ubuntu1
and seems that the problem is solved

thanks

[Titantux (israel-m-dj)]

Hi, 2 days a go I've updated from 16.04.4 to 16.10 and problem still, as @Dea1993 said got that version, but noticed than restarting just the nm-applet, bring to me all wifi networks again.. as on https://bugs.launchpad.net/oem-priority/+bug/1574347/comments/79

killall nm-applet && nm-applet &

[Dea1993 (andrea-deangelis93)]

i confirm that the problem still present on an updated ubuntu 16.10.
if i turnoff wifi and then i turn on again, nm-applet not shown wireless connections, and the icon of connection became the icon of ethernet (but nm is connected to wifi).

solve this problem

[tomcat1x5 (tomson-deactivatedaccount)]

This bug is still present in Ubuntu 16.10! Do you know if other desktop distributions like Fedora or openSUSE also have this bug?

[Peter Amaral (amaralpeter)]

Hi everybody, I realize that this fix I found may not help everybody. However, the symptoms I was seeing are the same as described in this bug report so maybe it will work for some other folks as well. The solution was to do the following:

$ sudo vim /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

Change the value of wifi.powersave to 0

:wq

After rebooting I have not experienced the problems with disconnect, even after resuming from suspend.

As I understand it, this setting will disable power management for wifi adapters if its not supported in the driver/kernel by default.

[Hansen (moteprime)]

The "wifi.powersave to 0" did not make any difference for me.

[tim__b (timb)]

Same problem with freshly installed Xubuntu Xenial 16.04.1 here.

[stavros daliakopoulos (stavrosd)]

Can ubuntu consider switching to Wicd or wicd is more buggy than networkmanager ?

[Scott Stensland (scottstensland)]

bug still happens in

network-manager 1.2.4-0ubuntu0.16.04.1

[MaTachi (matachi)]

larabi: I came from Fedora, and I had been running it for the last releases on my laptop. Never had any WiFi issues, so there's not anything wrong with my hardware. I recently installed Ubuntu 16.04.1 LTS, but these WiFi issues are quite annoying and I'm contemplating switching back to Fedora. I don't understand how this still hasn't been fixed in an LTS version of the OS.

[stavros daliakopoulos (stavrosd)]

The "HOW TO TEST A FIX" is meaningless.

nmcli dev

DEVICE TYPE STATE CONNECTION
wlp2s0 wifi connected Thomson_etc

but the applet still doesn't list any wireless network.

[Alberto Salvia Novella (es20490446e)]

@ Stavros Daliakopoulos

That simply means this report isn't related with your bug. Even when the consequences are the same, the causes aren't.

[Hansen (moteprime)]

If i set "All users may connect to this network" in 'network connections'for the used wi-fi connection, nm-applet does no longer crash when returning from suspend?

[rjb (ron-buehler)]

I can't confirm. unfortunately this doesn't do the trick for me.
What's different now is that the WiFi is already conected on the login screen with the arrow icon. As soon as I login, it's the WiFi icon. When I suspend and return I have arrows again.

[stavros daliakopoulos (stavrosd)]

bug still happens in

network-manager 1.2.6-0ubuntu1

[Tim Embler (nonparity)]

this issue still appears to be occurring. I am experiencing the same problem for the past two days.

[Tim Embler (nonparity)]

Also just to add I am using network-manager version 1.2.6-0ubuntu1

[Khoi (minhkhoitran2)]

Bug still occurs with network-manager 1.2.6-0ubuntu0.16.04.1

[Daniel van Vugt (vanvugt)]

All: Commenting on a closed bug will generally be ignored (even if it was closed erroneously).

If you have continuing issues then please log a new bug.

[loveme (lovemej)]

wifi disconnects frequently