cannot view wifi networks after re-enabling wifi

[hussain]

after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid.

[Shih-Yuan Lee (fourdollars)]

hussain, could you help to take a screenshot so we can realize the problem easier?

[Launchpad Janitor (janitor)]

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

[Hansen (moteprime)]

after returning from suspend, nm-applet needs to be restarted to show 'beam' icon and wifi items in networkmanager applet menu.

This bug are not at duplicate of bug #1574347, that has now been fixed.
We are a group of users that all subscribed to bug #1574347 but it ended up having several issues, that got fixed except this.

[SameOld (nikolay-ognyanov)]

I confirm that problems with the network manager as described above persist after the 1.2.0 update. For me the problems occur at random times and do not seem to be strongly correlated with suspend. If a wifi connection is already established then it usually continues to work even though the network manager does not display it (or any other available).

My system is Thinkpad T530 with an Intel 6205 wifi controller.

[Shih-Yuan Lee (fourdollars)]

Does anyone help to take a screenshot by `gnome-screenshot -i -d 5` when this issue happened?

[hussain (lovalim)]

as u can see from the attachment i m connected over wifi network, but still the icon is arrow up-down. each time i have to open network to select wifi. even i need to turn on and off wifi couple of time just to activate wifi.

[Henry J. Douglas (cyberdoug42-deactivatedaccount)]

Thanks for creating a new bug report. I am now using Xubuntu 16.04, and after the last updates from [#1574347](https://bugs.launchpad.net/bugs/1574347) bug report, network-manager became more unstable. Connection drops very often, even while I'm using it. Suspend? I've disabled it, since it causes up/down (Ethernet) arrows in the applet (with no Wifi APs on the list) and sometimes the connection drops along with that behavior. "sudo systemctl restart network-manager" is not always effective.

Intel Wireless 3160. Many fresh installs.

[Christian Heitjan (heitjan)]

Here's a screenshot of my two arrows. No Wifi network visible.

[Christian Heitjan (heitjan)]

And here's a screenshot taken of the network-information. The machine is connected to a Wifi-network.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Shih-Yuan Lee (fourdollars)]

Could you fix this problem by executing `sudo wpa_cli scan` manually?

[Hansen (moteprime)]

I'll see to reporting the bug upstream and post the number here.

[Hansen (moteprime)]

https://bugzilla.gnome.org/show_bug.cgi?id=767317

[Henry J. Douglas (cyberdoug42-deactivatedaccount)]

I'm being disconnected after leaving the computer idle for a minute or so. However, while downloading a large file or playing an online game, for example, the connection goes on and never quits. As soon as the downloads finish... it's gone. Network-Manager shows connected, but ownCloud sync stops, can't connect to websites or check for updates. To bring it back, I must reconnect to my AP. It's pretty annoying when combined with the suspend issue. Very bad bug. Hope this gets solved or I'll have to use Windows 10... and that's a game over.

[Henry J. Douglas (cyberdoug42-deactivatedaccount)]

It's now working, I think. Downloaded and installed latest linux kernel updates (listed below), restarted and performed several suspends without losing connection or list of APs. Please confirm.

Start-Date: 2016-06-09 23:06:05
Commandline: apt upgrade
Requested-By: cyberdoug (1000)
Install: linux-signed-image-4.4.0-24-generic:amd64 (4.4.0-24.43, automatic), linux-image-4.4.0-24-generic:amd64 (4.4.0-24.43, automatic), linux-headers-4.4.0-24:amd64 (4.4.0-24.43, automatic), linux-image-extra-4.4.0-24-generic:amd64 (4.4.0-24.43, automatic), linux-headers-4.4.0-24-generic:amd64 (4.4.0-24.43, automatic)
Upgrade: linux-headers-generic:amd64 (4.4.0.22.23, 4.4.0.24.25), linux-libc-dev:amd64 (4.4.0-22.40, 4.4.0-24.43), linux-image-generic:amd64 (4.4.0.22.23, 4.4.0.24.25), linux-signed-image-generic:amd64 (4.4.0.22.23, 4.4.0.24.25), linux-signed-generic:amd64 (4.4.0.22.23, 4.4.0.24.25), linux-generic:amd64 (4.4.0.22.23, 4.4.0.24.25)
End-Date: 2016-06-09 23:07:58

[Henry J. Douglas (cyberdoug42-deactivatedaccount)]

Sorry, false alarm. My very last attempt failed. Up/down arrows are back.

[hussain (lovalim)]

Any update

[Hansen (moteprime)]

No much, for some reason i haven't gotten notification mails from bugzilla, there's been a couple of responses but nothing that changes anything.
I'm not much experienced with the Bugzilla Gnome rutine, but maybe some of your could confirm the bug there to. But better keep it to the one bug with the applet that's missing the WiFi part.

[hussain (lovalim)]

OK thanks for the update.

[TT Mooney (ttm)]

I see the same problem when coming out of suspend:

Ubuntu 16.04 Unity, Dell XPS 13 9333 (Sputnik 3), Intel Wireless 7260.
Ubuntu 16.04 Unity, Lenovo Thinkpad X220, Intel Wireless 6205.

If I restart the network-manager service, it recovers until the next suspend:

sudo systemctl restart network-manager.service

On boot, the systems do show a list of wireless networks, but with the Ethernet connected icon. They are unable to join any WiFi network due to 'Insufficient privileges' and do not automatically join known networks. Once the user is logged in the applet works, until it is put into, and recovers from, suspend.

[Christian Dysthe (christian-dysthe)]

I also see the same problem coming out of suspend. Manually restarting network-manager with 'sudo systemctl restart network-manager.service' is a workaround but not a solution. I go in and out of suspend a lot with my laptop so this one is very annoying.

[hussain (lovalim)]

We all Are having the exact same issue

[SameOld (nikolay-ognyanov)]

Dear Ubuntu developer/maintainers, thank you for the great job you are doing!

However:

Regardless of what/where is the root cause of this bug, the net result is a critical usability flaw of YOUR product. So how come you are not proactive at all? How can it be that an allegedly stable (and an LTS at that) version of Ubuntu has a known critical usability flaw and nobody takes care of it for 2 months?

[Christian Dysthe (christian-dysthe)]

Inactive to change distro for now. Can't use Ubuntu on my laptop now for work. I really hope this will be fixed soon. I haven't had a problem like this in years in Ubuntu

[Hansen (moteprime)]

Hi.
there's a response on bugzilla with questions.
I have answered one, but need help with the other or/and confirmation, but i'm not skilled enough to perform the build test and are on vacation so could some of you please help answering the developer?

[Joakim Koed (vooze)]

Currently testing with network-manager 1.2.0-0ubuntu0.16.04.3 from proposed (should probably be out within the week, so it's in 16.04.1?) Have not been able to reproduce after 10 suspends. So I think it got fixed.

[SameOld (nikolay-ognyanov)]

Well, network-manager 1.2.0-0ubuntu0.16.04.3 was already published as an update a couple of weeks ago and it definitely does not solve the problem (for me).

[Joakim Koed (vooze)]

No. It was not. https://launchpad.net/ubuntu/+source/network-manager/1.2.0-0ubuntu0.16.04.3 still in proposed.

[Joakim Koed (vooze)]

Maybe you are thinking of network-manager-gnome?

network-manager/xenial-updates,now 1.2.0-0ubuntu0.16.04.2 amd64 [installed]
  network management framework (daemon and userspace tools)

network-manager-gnome/xenial-updates,now 1.2.0-0ubuntu0.16.04.3 amd64 [installed]
  network management framework (GNOME frontend)

[Mikko Pesari (mpesari)]

network-manager{,-gnome} both 1.2.0-0ubuntu0.16.04.3, problem still persists.

[Joakim Koed (vooze)]

Mikko: weird, I have tried many times with my laptop, can't reproduce anymore.

[Joakim Koed (vooze)]

did you also update the other libs? libnm-glib-vpn1, libnm-glib4, libnm-util2, libnm0? :)

[Joakim Koed (vooze)]

Okay, I stand corrected, it seems to be fixed for my laptop, but not desktop (I get the ethernet icon, even though I only se WiFi on it when rebooting. After logging in, it returns to wifi icon... Running nmcli dev, it indeed shows it's a wifi connection. Not sure why it works differently on my laptop.

[Christian Dysthe (christian-dysthe)]

Seems to be fixed for my Thinkpad X1 Carbon

[Christian Dysthe (christian-dysthe)]

Forget my previous comment. It happened again as I got home from work. No wifi networks available. Then I get the wired icon in the notification area and I am connected but no networks show up and there's no way I can get back to normal without a reboot. Ugh.

[Christian Heitjan (heitjan)]

Found this bugreport: Could this be our Problem?

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

[Joakim Koed (vooze)]

@Christian Dysthe: are you running .3 from proposed to test?

[Christian Heitjan (heitjan)]

No, I'm not using the proposed repositories.

Am Sa, 16. Jul, 2016 um 1:46 schrieb Joakim Koed <email address hidden>:
> @Christian Dysthe: are you running .3 from proposed to test?
>
> --
> You received this bug notification because you are subscribed to the
> bug
> report.
> https://bugs.launchpad.net/bugs/1589401
>
> Title:
> cannot view wifi networks after re-enabling wifi
>
> Status in NetworkManager:
> Confirmed
> Status in network-manager package in Ubuntu:
> Confirmed
>
> Bug description:
> after re enabling wifi, up-down arrows just like wired network.
> cannot
> see any wifi ssid.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions

[Christian Dysthe (christian-dysthe)]

@Joakim Koed: I wasn't when I wrote the comments above. I am now. It did work normally when I came home last night and went on my home network. I won't really know if this is fixed until next week when I start moving between networks with my laptop suspended in between.

[Christian Heitjan (heitjan)]

ok, all together, I just added the proposed repository. After a full
update was made, nothing has changed.

Still two arrow and no network to select...

Am Sa, 16. Jul, 2016 um 2:01 schrieb Christian Dysthe
<email address hidden>:
> @Joakim Koed: I wasn't when I wrote the comments above. I am now. It
> did
> work normally when I came home last night and went on my home
> network. I
> won't really know if this is fixed until next week when I start moving
> between networks with my laptop suspended in between.
>
> --
> You received this bug notification because you are subscribed to the
> bug
> report.
> https://bugs.launchpad.net/bugs/1589401
>
> Title:
> cannot view wifi networks after re-enabling wifi
>
> Status in NetworkManager:
> Confirmed
> Status in network-manager package in Ubuntu:
> Confirmed
>
> Bug description:
> after re enabling wifi, up-down arrows just like wired network.
> cannot
> see any wifi ssid.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions

[Joakim Koed (vooze)]

Strange :/ Anyway, until this is resolved, I can recommend my solution here: http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade/761220#761220

[Christian Dysthe (christian-dysthe)]

I have made an interesting observation. I only see this problem on my Lenovo Thinkpad X1 Carbon 1st Gen, but not with the X1 Carbon 2nd and 3rd Gen. I have all three and they are all running Ubunity 16.04 x64. So maybe this depends on the version of the wi-fi hardware? All these laptops have Intel wi-fi hardware, but newer versions in 2nd and 3rd Gen. I'm still having wi-fi hiccups after resume with the 1st Gen machine after adding proposed.

I'm trying @Joakim Koed 's script now.

[Cip Man (cipman-p)]

For me 'systemctl restart NetworkManager.service' fixes it until the next reboot - which is less than once a week, I only suspend the laptop.
So my workaround is to run it as cron job after reboot:

> sudo crontab -e

add the line:

@reboot sleep 10 && systemctl restart NetworkManager.service

This instructs the system to wait for 10 seconds after reboot and then restart the service; experiment with the 10 seconds, might not be enough for slower/older laptops.

[Joakim Koed (vooze)]

So .3 is out now. Could everyone affected maybe try and test the new one and see if they are still affected? It seems solved from here.

[Christian Heitjan (heitjan)]

All updates installed, still the same problem.

On gnome-bugs someone wrote:

"I can't see a problem with nm-applet icon neither on Arch Linux nor
Fedora. As far as I know, Ubuntu uses its own patches that may cause the
problem."

Any ideas?

Am 21.07.2016 um 16:39 schrieb Joakim Koed:
> So .3 is out now. Could everyone affected maybe try and test the new one
> and see if they are still affected? It seems solved from here.
>

[Peng (pengwg)]

For me it is improved from last update. Still happens just more rarely.

[SameOld (nikolay-ognyanov)]

Installed .3 together with all other updates. Still not working for me. Actually appears to work somewhat worse. The failures appear to be somewhat more frequent.

[Giovanni Mellini (merlos)]

After last updates I have the same problem when coming from suspend

[Joakim Koed (vooze)]

Sorry to hear it's not fixed for you guys. If anyone could build it without the patches ubuntu/debian applied that would help alot (i'm not a dev) I would, but build fails for me :/

If those it fails with: http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade/761220#761220 this will solve it for you, while we wait for devs to take a look at it.

[Mikko Pesari (mpesari)]

I installed network-manager-gnome version 1.2.2 available in yakkety. After preliminary testing (a couple of suspend cycles) it seems to have fixed the problem!

You can download binaries from https://launchpad.net/ubuntu/yakkety/+source/network-manager-applet or build it on xenial like this:

# apt-get install devscripts
# apt-get build-dep network-manager-applet
$ dget http://archive.ubuntu.com/ubuntu/pool/main/n/network-manager-applet/network-manager-applet_1.2.2-0ubuntu1.dsc
$ dpkg-source -x network-manager-applet_1.2.2-0ubuntu1.dsc
$ cd network-manager-applet-1.2.2
$ dpkg-buildpackage -uc -us
# dpkg -i *.deb

[Davide (tarski10)]

Sony VPCEB1M1E,
ubuntu 16.04.1 fresh install,
the problem seems solved.

[Joakim Koed (vooze)]

Mikko: you can just download the debs, no need to build it :)

[Mikko Pesari (mpesari)]

The problem still persists with network-manager-gnome 1.2.2 after all.

[Davide (tarski10)]

Mikko: Have you tried reinstalling using the new iso 16.04.1 ?
My experience:
Ubuntu 16.04.0 updated: I have the problem,
Ubuntu 16.04.1: the problem is solved,
strange but true.
I also noticed a reduction in startup time.

[lauricat (lauricat)]

Mikko:

I have installed the new network-manager-gnome 1.2.2 as suggested, as well as [last week] the latest stable kernel - 4.6.3

So after a dozen suspend-resume cycles I can report so far so good!

But no willing to say fixed until I give it some more time, say a week of normal use.

Yes - I have also noticed a reduction in start up time.

[Christian Heitjan (heitjan)]

I found out, that the bug appears even if I disable wifi with the
hardware key. After re enabling wifi I got the two arrows. No network to
select.

[Joakim Koed (vooze)]

Christian Heitjan, the hardware does one of the following things:

sudo modprobe -r wl; sudo modprobe wl
rfkill block wlan; rfkill unblock wlan

You need to:

sudo systemctl restart network-manager.service, since the bug is in network manager and not the wifi card.

[lauricat (lauricat)]

****************************************************************************************************
Mikko:

I have installed the new network-manager-gnome 1.2.2 as suggested, as well as [last week] the latest stable kernel - 4.6.3

So after a dozen suspend-resume cycles I can report so far so good!

But no willing to say fixed until I give it some more time, say a week of normal use.

Yes - I have also noticed a reduction in start up time.
*****************************************************************************************************

Further to this post I made, I have to retract that statement to say the fault still occurs.

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 --
xxx@xxx-ThinkPad-X220:~$

Also, 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...

[Joakim Koed (vooze)]

Can also report the problem is still present with clean install :/

Really don't want to upgrade to yekkety when that is released, but stay with xenial until 18.04. Can't ubuntu devs start testing and trouble shooting this?

[Joakim Koed (vooze)]

It has recently started happening on the lock screen, before logging in, as well :/

[Mathieu Trudel-Lapierre (cyphermox)]

Joakim, please file your own bug report (or point to yours if you already created one). Despite things looking similar, it doesn't mean it's the same issue. There are many different failure scenarios for NetworkManager and wireless devices, some of which are caused by devices failing to scan appropriately on their own after resume.

[Mathieu Trudel-Lapierre (cyphermox)]

In general, please run 'sudo iw dev wlan0 scan' (or a variation of this command with the right interface name for your system). Your system should, from there, show scan results in the nm-applet menu.

If this *does not* solve your issue, please file a new bug report, and report here what the number is. Do not reuse some other bug report someone else may have filed; even though things look the same, doesn't mean they are.

If this works, we've effectively established that the issue is in the scanning logic. We've looked at the code in NetworkManager before, and these issues seem to be more prevalent in Intel hardware, which makes me suspect the Intel firmware a whole lot -- which means we're not any more advanced in solving this issue than before. Doesn't mean NM isn't wrong, just that the more likely culprit is the kernel or firmware. There are already many bugs open on this.

If you're seeing this issue, but you're not using an Intel wireless card, then please speak up, so we know whether to look at other pieces of the system.

[Mathieu Trudel-Lapierre (cyphermox)]

The linked upstream bug was gnome-bugs #767317, removing for now until we can isolate *one issue per bug*, rather than be looking at multiple different things all dumped in one large heap of comments.

Again, if you think you're seeing this issue, please file *your own* bug; it's easy for developers to mark bugs as duplicate, but much harder to split them up.

[Joakim Koed (vooze)]

Mathieu Trudel-Lapierre:

I don't think you can expect all people affected by this (alot!, I have probably helped 10 people on reddit, and many on askubuntu, see http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade/761220#761220)

That being said, I have some new information for you. Regarding this bug (not the one with lockscreen!)

- I CAN'T reproduce with broadcom, seems you might be right about Intel wifi.
- With Intel I can reproduce right after a reboot with using suspend from menu or losing the lid.
- sudo systemctl suspend does not seem to be affected. Strange as that is.

I have also downloaded all the new firmware drivers from kernel and put in /var/lib/ it was messing quite a few, dmesg with errors. Same problem.

Hope this helps you :)

[Joakim Koed (vooze)]

Okay new information.

If I restart network-manager right after booting (before suspend) I can't reproduce.

So maybe make a script to delay network-mananger at boot with solve all problems?

[James Bowery (jabowery)]

Confirmed here and none of these "work-arounds" worked for me:

# systemctl restart network-manager.service
# nmcli g
# killall nm-applet
# start nm-applet
start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

I'm running:

~# dpkg -l | grep network-manager
ii network-manager 1.2.0-0ubuntu0.16.04.3 amd64 network management framework (daemon and userspace tools)

With a Belkin dongle model f7d1101v1

# lshw -class network
Shows no "product: ..." attribute but does show:

*-network
...
       configuration: broadcast=yes driver=r8712u multicast=yes wireless=unassociated

[Peter S (peter-sevemark)]

A complete re-installation of the entire operating system seems to have done the trick for me (call it a workaround if you want)! I used the exact same source (i.e. Ubuntu 16.04.1 LTS 64 bit from a USB stick) and connecteded my wifi during installation. I also restored my home folder (including configuration files). Voilà, no longer any arrows in the applet tray or other connection issues! The network also returns immediately after suspend. I have only used this configuration for two days, so I can't leave any guarantees. I will return, though, if any errors reoccur.

[Joakim Koed (vooze)]

I just tested with the new 1.2.2 network-manager from proposed. Same result.
Even tried creating a new user, same result.

Peter S:
Can you try the following:
- Reboot the machine and login.
- Then suspend, either by closing the lid or pressing the suspend in the menu. (running suspend in terminal does not seem to be affected.)

The reason I want you to do this, is because of you restart network-manager before suspending, it does not seem to make the ethernet-icon appear.

Relevant: Is ubuntu using upstart to suspend, when pressing suspend and closing the lid, instead of systemd-suspend? This could be the reason.

[Peter S (peter-sevemark)]

It keeps working after reboot and suspend. I'm not sure exactly which kernel version I used to run before re-installing, but this one is called 4.4.0-34-generic.

[Joakim Koed (vooze)]

Peter: Thanks for trying. I run the same kernel etc. etc. but it keeps happening for me.
Well, for me, it's not a big deal, since I just use my script from here: http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade/761220#761220 but for new users, it can be quite annoying.

[Christian Heitjan (heitjan)]

I found out, that after installing the latest updates and REBOOTED the
bug is gone. No more arrows, and connection establishes directly.
For me the bug can be closed as "soled"

[Dmitry Gutov (dgutov)]

Likewise, I've seen it before, but not for a while now.

[Peter S (peter-sevemark)]

The arrows are gone for me too now (after reinstalling, I think), but there are still connectivity issues. Either one has to wait a minute or two for a wifi connection after bott up or put it in suspend mode (close the lid) to establish a wifi connection.

[Hansen (moteprime)]

Are there any progress on this bug, i still have to runs scripts several time a day to get the applet working.

[Henry J. Douglas (doug-the-alquimista)]

The arrows are not gone. I just made a clean install and update.

[Peter S (peter-sevemark)]

Have any of you tried using static IP adressess for your system?

[Joakim Koed (vooze)]

Peter S: Just tried, same result.

[Christian Dysthe (christian-dysthe)]

I am having the same problem in Ubuntu 16.10 Beta 1. The main reason I went for it so early was hoping these issues were resolved. They are not. There's always problems when I come home after work and resume my laptop. I'm either stuck on the now non existing work network or I do not have any networks at all. I have tried "everything". I have two of these Yoga Pro laptops, one with vanilla Ubuntu 16.10 beta and one with UbuntuGNOME. On UbuntuGNOME no such problems.

[Joakim Koed (vooze)]

Christian: Sounds like maybe it could be a problem with network-manager + lightdm, as gnome use GDM it makes sense there is no issue there.

In the meantime, you could always use this script: http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade/761220#761220

[Peter S (peter-sevemark)]

Thanks for the input about 16.10, Christian. I was considering an upgrade to get rid of the problem, but now I will think twice before doing so.

[Peter S (peter-sevemark)]

I still have the same issue, even after enabling static IP.

[Mathieu Trudel-Lapierre (cyphermox)]

If you have issues with wireless not coming up after suspend, please run 'sudo iw dev wlan0 scan', and see if the applet then changes (it may take a few seconds) to wireless and displays the list of APs. It does not seem to me like any other workarounds are likely to work for everyone.

If you have any scripts that restart NetworkManager or the applet, please remove them for testing the above workaround, and to file a new bug -- otherwise things aren't as clear as they should be for us to understand what is going on.

The issue appears to be limited to the Intel driver, so people should *most definitely* file their own separate bug reports against "linux", so that we can know exactly each of the different models of wireless cards are affected.

[Jeremy LaCroix (j-jlacroix)]

Running 'sudo iw dev wlan0 scan' does work around the issue for me. I have this issue on two computers, they have the following wireless cards from Intel:

Intel Wireless 7260 (rev bb)
Intel Wireless 7260 (rev 73)

Just to be clear, should I be creating a new bug for each of these two cards? Would this be the 'linux' package, or 'iwlwifi'?

[Peter S (peter-sevemark)]

I have Intel Wireless 3165 (rev 81)

[Dan Large (dlarge-awesomejar)]

I have an X1 Carbon Gen1 with Intel Centrino Advanced-N 6205 [Taylor Peak] (rev 96).
'sudo iw dev wlan0 scan' doesn't help. I usually have a blank wireless icon (no bars) with no networks listed, occasionally the up-down arrow wired connector icon. Need to go to System Settings > Network to see what I'm connected to.

[monte (monte3)]

Centrino Advanced-N 6205 here too. I have different issues from time to time, I'd rather say I have every one described on this page. But they happen without some strict manner, the only thing for sure is that after every suspend I have to restart nm-applet to bring it back to normal work.

[Hansen (moteprime)]

I have been running a manual script ten times a day for half a year to live with this bug.
The bug I reported upstream are either waiting for us here on launchpad or the bug's not being taken serious. Are there anyone reading this that knows anything about how we can get this fixed, I don't have the experience or the skills to set things in motion.
It does seem like there only a handful of us regular users that's aware of this problem.
Please anyone?

[Peter S (peter-sevemark)]

'sudo iw dev wlan0 scan' (or in my case wlp13s0 instead of wlan0) doesn't work for me. Here's the output:

command failed: Device or resource busy (-16)

[Hansen (moteprime)]

Well for what it's worth the bug seems to be fixed in 16.10

[Peter S (peter-sevemark)]

Just made a fresh installation of Ubuntu 16.04 and then upgraded to 16.10 through APT. I'm running kernel 4.8 and see no improvement whatsoever in 16.10.

This bug is not fixed in any way, shape or form.

[Christian Dysthe (christian-dysthe)]

I've also upgraded to 16.10 and see the same issues. There's also other networking issues on my laptops that wasn't present in 15.10. Seems that Wi-Fi and networking was fundamentally broken in 16.04 and now carries over to 16.10

[Carlo (woddy68)]

Not stand it anymore this gnome network managers.
Buggy, Buggy.

[Anders J (andersj23)]

I'm seeing the same problem on a Thinkpad T450s with "Intel Corporation Wireless 7265 (rev 59)" (iwlwifi) on Ubuntu 16.04.1, all packages up-to-date as of time of writing:

Kernel 4.4.0-43-generic
network-manager 1.2.2-0ubuntu0.16.04.3
network-manager-gnome 1.2.0-0ubuntu0.16.04.4

This is a bog-standard install with all the defaults (i.e. LightDM, Unity, ..).

(I have also tried all this with my normal setup, which is booting to console (no LightDM) and using startx to start i3 (no Unity). Exact same issue.)

On laptop resume wifi connection still works but nm-applet no longer shows a list of available wifi networks. However, 'nmcli dev wifi list' *DOES* show the normal list of the couple of dozens networks around me.

The suggested workaround 'sudo iw dev wlan0 scan' (or, for me, wlp3s0) has no effect. It shows info about the networks in the console but changes nothing in nm-applet.

If I simply kill nm-applet and start it again, everything is fine. (I saw someone above killing nm-applet and starting it as root. You should start it as your normal user.)

I came up with a simple workaround. If you're in the same boat (i.e., if "killall nm-applet && nm-applet &" makes it work again), the following might work for you too. Add the following to a new file, /lib/systemd/system-sleep/fix-nm-applet, replacing yourusername with whatever user you're logged in to X as:

#!/bin/sh
USER=yourusername
export DISPLAY=:0

case $1 in
  post/*)
    su $USER -c 'killall nm-applet; sleep 4; nm-applet' &
    ;;
esac

Then make it executable: chmod +x /lib/systemd/system-sleep/fix-nm-applet

Then try suspending and resuming. The script simply kills nm-applet on resume, waits 4 seconds, and starts nm-applet again. (It appears that nm-applet will still b0rk if executed too early after resume, thus the sleep -- if it doesn't work, try a higher value.)

It's an ugly solution (I also tried to do it as a systemd service, but no dice, and my patience was running low) -- but it's the best I've got at the moment...

[Anders J (andersj23)]

Sorry, spoke a bit to soon. My workaround above doesn't actually work when I do LightDM+Unity, only when I do text boot (i.e. when I've done systemctl set-default multi-user.target (instead of graphical.target)), and start i3 with startx.

(Actually, when running Unity, the script *does* execute and *does* kill and start nm-applet again, but nm-applet doesn't show up as an icon in the taskbar. I don't know why.)

systemctl restart network-manager always fixes the issue and can easily be put in a systemd unit file (see e.g. https://gist.github.com/nitely/3d5f10b4f686f5f96c95), but that seems rather heavy when it's just nm-applet that needs restarting, at least in my case.

Also, I seem to have made a mistake in the script above - change post/*) to post)

[Henry J. Douglas (doug-the-alquimista)]

I'm running Ubuntu 14.04.5 for now. It's unaffected by this. The .5 release added the support I needed. None of the workarounds for 16.04 worked in this hardware.

[mattebuntu (mattebuntu-deactivatedaccount-deactivatedaccount)]

I'm using a Toshiba laptop with a Qualcomm Atheros AR8152 network card and the bug affects me too. It also happens if the connection is lost abruptly or WiFi is turned off

[Quang (quang)]

I'm using a Dell Lattitude E6230 with Intel wireless card (Centrino Advanced-N 6205 [Taylor Peak]). On Ubuntu 16.04 this bug affected (wifi icon changed to two arrows, network manager could not be controlled, have to be relaunched). But since upgrading to Ubuntu 16.10 for the past week I have not seen this bug after dozens of suspends.

[Sander Jonkers (jonkers)]

I have the same problem with a fresh install of Ubuntu 16.10 / yakkety on my HP Stream 13.

The workaround "sudo systemctl restart network-manager.service" works for me: it removes the up-down-arrow, and gives back the beam symbol showing the available wifi networks.

I have no file /etc/systemd/system/wifi-resume.service, so I can't use the workaround from http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade/761220#761220

FWIW: I've an Intel Wifi too:
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter

[Sander Jonkers (jonkers)]

FWIW2:

I only have Wifi. No fixed ethernet. Maybe that is part of the problem? Maybe the indicator assumes the first ethernet is always fixed ethernet, and puts that symbol on it?

[Joakim Koed (vooze)]

Sander: You don't need to have to file wifi-resume.service already.. nano will create it for you.. Just read what I wrote on askubuntu and do that ;) it will work.

[Sander Jonkers (jonkers)]

@Joakim: Ah, OK, I now understand. Thanks.

However: I have the beam symbol, but it's now grey (like: no signal), and no Wifi networks visible. :-(
After a "sudo systemctl restart network-manager.service" the beam signal shortly becomes an empty pizza slice, then the Up-Down-arrow, and greyed beam after a minute or so. Pity

And I should have written:
FWIW: I've NO Intel Wifi, but Realtek:
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter
Sorry about that.

[tomcat1x5 (tomson-deactivatedaccount)]

Is Ubuntu working on this bug? It's not the first release this problem happens. I have the same problem with a RTL8723be.

[Hansen (moteprime)]

No, nothing i know of is happening to solve this bug.
The bug report on bugzilla seems to wait on this bug report and nobody are working in it here.
I have tried to contact a couple of people to get some attention to it but to no avail.
If anybody know of any way to draw attention to this bug please help.

[rjb (ron-buehler)]

As requested by Mathieu Trudel-Lapierre (cyphermox) I have filed my own bug report in bug #1636282

[Dave Chiluk (chiluk)]

With my recent update to Yakkety I no longer seem to be experiencing this issue.

[rjb (ron-buehler)]

Dear all,
I have discovered something that may not have been reported in here so far:
After a fresh boot, when you suspend the machine, there will be arrows after waking up.
If you do "service network-manager restart" once, you'll get the WiFi icon back. From now on you can suspend as many times you like, the WiFi icon will stay there!
However, the next time you reboot all this magic is gone.

Can anyone reproduce this?

[rjb (ron-buehler)]

After performing some more tests:

The triggers for the network-manager showing the arrow icon and no WiFi networks are:
- Suspend mode (suspend/wake up)
- Hardware wireless button (turn WiFi off/an)
- Wireless network in network-manager GUI (deactivate/activate)
- Network in network-manager GUI (deactivate/activate)

btw: Lock screen has no influence.

When I do "service network-manager restart" once (independent of network-manager state) I'm getting rid of the problem. After this I can do everything listed above without loosing the WiFi icon and I'm always able to see the wireless networks around.

As soon as I do any of this, it's back to default (meaning that next time you do anything of the listed actions above, the arrow icon will appear and you won't be able to see other wireless networks:
- reboot
- shut down and boot
- log out and log in

Again: Lock screen has no influence.

[Hansen (moteprime)]

Could all you guys please click "This bug affects me" so we can get some action on solving this on the new report.

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

[Peter S (peter-sevemark)]

I'm starting to doubt that network-manager is the root of all this mess. Have any of you tried using WICD instead (an alternative network manager)? I seem to have the same connectivity issues there. And just as with network-manager, they appear at random.

Here's an instruction:
https://help.ubuntu.com/community/WICD

I still consider this a bug though, since all my other devices on the same wifi network are working flawlessly. Couldn't it be some bad implementation of the Intel Wifi driver within the kernel?

[Alexander Chepurko (alexander-chepurko)]

@peter-sevemark Yep, same exact problems with WICD means it's the wireless driver/kernel. Probably why no one is looking at this bug seriously.

[Dave Chiluk (chiluk)]

I spoke too soon still exists in Yakkety.

[Peter S (peter-sevemark)]

I'm eager to hear other members of this thread sharing their experience with WICD (see #109 for installation intructions). Especially those with a Intel wifi chip. If the the same connectivity issues remain in WICD, I assume we could abandon the idea that these issues are to be derived to network-manager, couldn't we?

[Hansen (moteprime)]

Shouldn't i close the bugzilla report already, it's seems dead anyway.
Will it change anything, making the bug unassigned?

[Peter S (peter-sevemark)]

If people keep whining about bugs in network-manager, without even trying WICD (or the like) for a couple of weeks, this thread is meaningless!

I'm still not sure that the problems I experience are completely unrelated to network-manager. I seem to have a more stable connection with WICD, so far. But I have to try it for another few weeks before I can say anything for sure.

[Hansen (moteprime)]

On Bugzilla one ask's:
-----------
It would be useful to have also NM logs. Would you please set:

  [logging]
  level=TRACE

in /etc/NetworkManager/NetworkManager.conf, restart the NM service, reproduce the issue and then attach the journal log ('journalctl -u NetworkManager -b')? Thanks!

[Sander Jonkers (jonkers)]

@Hansen ... I did that, did a reboot, did a suspend/resume (arrows appeared), and the logging is 1997 lines long. Can you advice what to do with that logging?

[Hansen (moteprime)]

@Sander Jonkers (jonkers) I'm not really very skilled but just a regular user that does whatever i can to get this bug fixed.

Can anybody help, and please join at bugzilla.
https://bugzilla.gnome.org/show_bug.cgi?id=767317

[ghuisman (geert-huisman)]

@Peter S (peter-sevemark):

First of all I agree on your comment #114: We need to test suggested scenarios so we can converge to a solution or approach to tackle the issue.

So I have installed WICD (conform issue #109) and removed the default network manager.
summary of my issue: in most cases no wifi connection after suspend and no possibility to make a new connection. I am using a Lenovo X220 with Ubuntu 16.04.

WICD gives me the opportunity to enable the WIFI connection after suspend. however I have to do it manually by starting the WICD application. The setting to make a connection automatically does not work.

I will test the robustness of WICD in relation to my issue further
Do you have a solution for the fact that WICD does not connect automatically?

Thanks
Geert

[taiebot65 (dedreuil)]

mm i am experiencing problems also since upgrading to 16.10. I m oppening a new bug Bug #1641154. I have the feeling that the device does connect to the network but the kernel crashes when establishing the connection this is the dmesg output when coming back from suspend

 wlan0: authenticate with 30:b5:c2:ad:b1:58
[ 149.927996] wlan0: send auth to 30:b5:c2:ad:b1:58 (try 1/3)
[ 149.929721] wlan0: authenticated
[ 149.932293] wlan0: associate with 30:b5:c2:ad:b1:58 (try 1/3)
[ 149.976858] wlan0: RX AssocResp from 30:b5:c2:ad:b1:58 (capab=0x431 status=0 aid=5)
[ 149.978961] wlan0: associated
[ 149.979027] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 150.042048] ------------[ cut here ]------------
[ 150.042115] WARNING: CPU: 0 PID: 880 at /build/linux-0gM0c3/linux-4.8.0/drivers/gpu/drm/i915/intel_display.c:1244 assert_cursor.constprop.127+0xe1/0xf0 [i915]
[ 150.042116] cursor on pipe A assertion failure (expected off, current on)
[ 150.042117] Modules linked in: ccm arc4 snd_hda_codec_si3054 snd_hda_codec_idt snd_hda_codec_generic snd_hda_intel rtl8187 snd_hda_codec mac80211 snd_hda_core snd_hwdep snd_pcm bluetooth zram snd_seq_midi snd_seq_midi_event snd_rawmidi cfg80211 coretemp pcmcia snd_seq joydev input_leds serio_raw snd_seq_device eeprom_93cx6 snd_timer yenta_socket lpc_ich snd tifm_7xx1 pcmcia_rsrc pcmcia_core tifm_core shpchp soundcore mac_hid binfmt_misc parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops firewire_ohci psmouse drm firewire_core ahci pata_acpi libahci sky2 crc_itu_t video fjes
[ 150.042171] CPU: 0 PID: 880 Comm: Xorg Tainted: G W 4.8.0-27-generic #29-Ubuntu
[ 150.042172] Hardware name: Gateway ML6226B / , BIOS 77.10 03/06/2007
[ 150.042175] c6b54967 c8e0f2b6 00000286 f168fa00 c63da625 f168fa44 f8b73798 f168fa30
[ 150.042180] c6071b9a f8b75b5c f168fa64 00000370 f8b73798 000004dc f8afdaa1 000004dc
[ 150.042185] f5660000 00000041 f559b000 f168fa50 c6071c06 00000009 00000000 f168fa44
[ 150.042191] Call Trace:
[ 150.042199] [<c63da625>] dump_stack+0x58/0x73
[ 150.042203] [<c6071b9a>] __warn+0xea/0x110
[ 150.042244] [<f8afdaa1>] ? assert_cursor.constprop.127+0xe1/0xf0 [i915]
[ 150.042246] [<c6071c06>] warn_slowpath_fmt+0x46/0x60
[ 150.042287] [<f8afdaa1>] assert_cursor.constprop.127+0xe1/0xf0 [i915]
[ 150.042328] [<f8b00a08>] intel_disable_pipe+0x48/0x260 [i915]
[ 150.042360] [<f8565542>] ? drm_crtc_vblank_get+0x12/0x20 [drm]
[ 150.042399] [<f8af7a33>] ? assert_vblank_disabled+0x13/0x70 [i915]
[ 150.042440] [<f8b03900>] i9xx_crtc_disable+0x70/0x480 [i915]
[ 150.042480] [<f8af9a43>] ? intel_crtc_disable_planes+0xc3/0xd0 [i915]
[ 150.042521] [<f8b07668>] intel_atomic_commit_tail+0x148/0x1050 [i915]
[ 150.042526] [<c61db897>] ? kmem_cache_alloc_trace+0xc7/0x1a0
[ 150.042547] [<f8500784>] ? drm_atomic_helper_setup_commit+0x2a4/0x300 [drm_kms_helper]
[ 150.042558] [<f8500784>] ? drm_atomic_helper_setup_commit+0x2a4/0x300 [drm_kms_helper]
[ 150.042569] [<f84fe198>] ? drm_atomic_helper_swap_state+0x1b8/0x2d0 [drm_kms_h...

[Shih-Yuan Lee (fourdollars)]

Hi,

I made some proposed fix for this issue in ppa:fourdollars/lp1589401 for xenial.
Please help to check if it works or not.

[Peter S (peter-sevemark)]

@ghuisman:

I tried WICD for a few of weeks. My experiences were the same as yours.

[Elad Hen (eladhen2)]

Testing Linux Mint MATE 18.1 BETA and having this bug. It was also present on Linux Mint MATE 18. Just installed WICD and it doesn't have this problem and it shows the access point around me after resuming from suspend.

[Oleg "Nightwing" Lomakin (nightwing666)]

network-manager 1.2.2-0ubuntu0.16.04.3 and network-manager-gnome 1.2.0-0ubuntu0.16.04.4 still had this bug.
Only nm-applet restart help

[Anders Frisk (anders-frisk650)]

@fourdollars, I installed your ppa in #120 above. Unfortunately I could not detect any significant change compared to the latest released versions. Following are my notes from my tests. The test PC has a fresh Ubuntu 16.04 install with all updates. The wifi interface name is wlp1s0 and there is no wired ethernet hw in the PC.

First tests done before installing the test ppa.
The tests where run in the exact sequence as listed.
  Action. - Result
1 Initial start of PC. - nm-applet ok
2 Radio HW off-on. - nm-applet not connected, no APs listed
3 service network-manager restart. - after long delay (>30s), connected, APs listed
4 suspend/resume. - not connected, no APs listed
5 service network-manager restart. - nm-applet ok
6 radio HW off-on. after long delay, works ok, APs listed
7 suspend/resume. - after long delay, works ok, APs listed
8 radio hw off-on. - nm-applet ok
9 shut down

10 start PC. - nm-applet ok
11 disable/enable networking (nm-applet menu option). nm-applet shows up/down arrow, no APs 12 listed, connection working
12 service network-manager restart. - nm-applet ok
13 suspend/resume. - nm-applet ok
14 disable/enable networking. - long delay until connecting, APs listed
15 Shut down

Started PC
Installed fourdollars ppa and verified that "test1" versions had been installed.

16 Restarted PC. - nm-applet ok
17 radio hw off/on. - nm-applet not connected, no APs listed, after very long delay up/down arrows
18 killall nm-applet && nm-applet & exit. - nm-applet ok
19 radio hw off/on. - not connected, no APs listed, after long delay up/down arrows, connection working
20 service network-manager restart. - nm-applet ok
21 suspend/resume. - nm-applet ok
22 disable/enable networking. - nm-applet ok
23 suspend/resume. - nm-applet ok
24 shut down

25 start PC. nm-applet ok
26 suspend/resume. - up/down arrows, no APs listed, connected
27 killall nm-applet && nm-applet & exit. - nm-applet ok
28 suspend/resume. - up/down arrows, no APs, connected
29 service network-manager restart. - nm-applet ok
30 radio hw off/on. - nm-applet ok

31 Restart PC. - nm-applet ok
32 radio hw off/on. - not connected, no APs listed
33 killall nm-applet && nm-applet & exit. - not connected, no APs listed
34 service network-manager restart. - long delay until connected, APs listed
35 radio hw off/on. - nm-applet ok

I hope these tests can be of some use... as noted earlier, it appears as if the problem goes away after "sudo service network-manager restart". The "killall nm-applet && nm-applet & exit" will make the nm-applet work ok, but only until next disabling event be it suspend/resume, hw switch off/on or sw disable/enable.

In addition to this documented test I have experienced the two problem symptoms (no wifi connection and or incorrect network icon and no APs listed in the nm-applet) on 7 different PCs all with Ubuntu 16.04 with latest updates. All the PCs have different HW (incl wifi) and are of widely different ages. In fact I only have one PC that has not exhibited any of the problems. That PC is running Lubuntu 16.04.

It is my experience that the "sudo service network-manager restart" command will correct the problem situation about 70% of the times and...

[Peter S (peter-sevemark)]

@anders-frisk650

Well done! Now we're getting somewhere.

[James Bowery (jabowery)]

First of all, you just cost me a few hours trying to get my network
connection back after the instructions for reinstall of network-manager
upon failed WICD, themselves, failed.

Second, if the default network manager system that comes with distributions
has a bug, it's not "whining" to rather insist that it be fixed or replaced
with something that works.

On Sat, Nov 5, 2016 at 3:50 AM, Peter S <email address hidden> wrote:

> If people keep whining about bugs in network-manager, without even
> trying WICD (or the like) for a couple of weeks, this thread is
> meaningless!
>
> I'm still not sure that the problems I experience are completely
> unrelated to network-manager. I seem to have a more stable connection
> with WICD, so far. But I have to try it for another few weeks before I
> can say anything for sure.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1589401
>
> Title:
> cannot view wifi networks after re-enabling wifi
>
> Status in NetworkManager:
> Confirmed
> Status in network-manager package in Ubuntu:
> Incomplete
>
> Bug description:
> after re enabling wifi, up-down arrows just like wired network. cannot
> see any wifi ssid.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions
>

[mr.lahorde (mr-lahorde)]

Same issue on arch.
As a workaround you can create this systemd unit :

[Unit]
Description=System resume actions
After=suspend.target

[Service]
Environment=XAUTHORITY=/home/user_name/.Xauthority
Environment=DISPLAY=:0.0
Type=simple
ExecStart=/usr/bin/bash -c "killall nm-applet && sudo -E -u user_name /usr/bin/nm-applet"

[Install]
WantedBy=suspend.target

[Saha (smirta)]

Same thing. The list of wifis refreshes only after nm-applet is restarted.

[Tanner Blomster (blomstertj)]

When my laptop was on Ubuntu I just needed the service to restart network manager. When switching to Xubuntu that service no longer works. Even after restarting network manager the icon is still showing Ethernet and no WiFi networks are listed. This bug only happens after very long suspends. Restarting the applet manually fixes my issue now.

[Tanner Blomster (blomstertj)]

I should add that after resume my WiFi connection is still working and I can browse the Internet fine. The problem is the applet displays the wrong icon and no APs are listed.

[Jeremy LaCroix (j-jlacroix)]

Again, you shouldn't need to restart network manager or the applet. You can simply rescan your wireless networks manually.

sudo iwlist <interface> scan

The applet should be doing this as soon as the machine wakes up, but it's clearly not.

[James Bowery (jabowery)]

iwlist didn't work on my system. Nothing did. I finally gave up and
bought another interface.

On Thu, Jan 19, 2017 at 2:02 PM, Jeremy LaCroix <email address hidden>
wrote:

> Again, you shouldn't need to restart network manager or the applet. You
> can simply rescan your wireless networks manually.
>
> sudo iwlist <interface> scan
>
> The applet should be doing this as soon as the machine wakes up, but
> it's clearly not.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1589401
>
> Title:
> cannot view wifi networks after re-enabling wifi
>
> Status in NetworkManager:
> Confirmed
> Status in network-manager package in Ubuntu:
> Incomplete
>
> Bug description:
> after re enabling wifi, up-down arrows just like wired network. cannot
> see any wifi ssid.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions
>

[Hansen (moteprime)]

Can anybody confirm this:

In 'network connections', if the setting "All users may connect to this network" are set for the used wi-fi connection, nm-applet will no longer crash when returning from suspend?

Any idea why?

[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.

[Diego Liedo (diegoliedo)]

I too have this bug on a Lenovo W520 with Ubuntu 16.04 kernel 4.4.0-62-generic
The only solution that has worked is restarting the network-manager service, however if I attach an USB WiFi adapter based on rtl8187, the icon becomes normal and I can choose a network for that adapter. The Intel Centrino Advanced-N 6205 remains unusable.
Also the interface name is wlp3s0 instead of the usual wlan0 on other installations I've made.
If I try $ ifdown wlp3s0 results in Unknown interface wlp3s0
As to comment #133 nm-applet still crashes after hardware switching off/on WiFi and resuming from suspend.

[monte (monte3)]

Please try network-manager-1.2.6 from xenial-proposed, if you have 16.04. For me it seems to fix this bug. But when you will test don't forget to turn off all self-made scripts to see if it really does the job.

[Douglas Silva (o-alquimista)]

Any change after 16.04.2? New kernel 4.8...

[Peter S (peter-sevemark)]

All of you who are affected by this bug, try the following: Change the beacon interval on your router to the lowest value possible.

[Jeremy LaCroix (j-jlacroix)]

Why do that? This is a bug with Network Manager, not our routers.

[Hansen (moteprime)]

Yes, this bug is not related to beacon intervals on the router.

[Peter S (peter-sevemark)]

It definitely could be. Personally, I think many of the issues mentioned above are completely unrelated to Network Manager. Those cases should be excluded from a bug report. Therefore I suggest that everyone who's having problems check their beacon interval settings.

[Jeremy LaCroix (j-jlacroix)]

Network Manager is the culprit, not anyone's routers. This is evident by the fact that earlier versions of Ubuntu didn't experience this issue, this issue happens regardless of which router we're connecting to, it happens regardless of which location we are at, and the underlying issue is that Network Manager cannot see ANY access points, not just the one we normally connect to. There is literally no scenario in which it is someone's router that is causing this.

[James Bowery (jabowery)]

After I gave up and shifted to a wired connection, I noticed that I'd get
disconnected periodically but then it would reconnect successfully. It
seems some drivers manage to reconnect and other drivers don't.

So there may be _two_ bugs:

1) A bug that results in occasional loss of connection.
2) A bug in one or more drivers that disables automatic reconnection.

On Wed, Mar 1, 2017 at 9:42 AM, Jeremy LaCroix <email address hidden>
wrote:

> Network Manager is the culprit, not anyone's routers. This is evident by
> the fact that earlier versions of Ubuntu didn't experience this issue,
> this issue happens regardless of which router we're connecting to, it
> happens regardless of which location we are at, and the underlying issue
> is that Network Manager cannot see ANY access points, not just the one
> we normally connect to. There is literally no scenario in which it is
> someone's router that is causing this.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1589401
>
> Title:
> cannot view wifi networks after re-enabling wifi
>
> Status in NetworkManager:
> Unknown
> Status in network-manager package in Ubuntu:
> Incomplete
>
> Bug description:
> after re enabling wifi, up-down arrows just like wired network. cannot
> see any wifi ssid.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions
>

[Daniel J Blueman (watchmaker)]

I have observed this issue on both Broadcom and Atheros (ath10k) wireless cards, and even reproduced it on the current stable 4.9.13 kernel, thus it would appear to be a higher-level issue. Running 'sudo iw dev wlan0 scan' works around it every time.

[Daniel J Blueman (watchmaker)]

I have only seen this when resuming from suspend.

For the upstream developers, we need to add to /etc/NetworkManager/NetworkManager.conf:
[logging]
level=TRACE

Then restart, and when the issue is observed, capture the networkmanager logs with:
journalctl -u NetworkManager -b

and put into:
https://bugzilla.gnome.org/show_bug.cgi?id=767317

[Daniel J Blueman (watchmaker)]

When resuming from suspend and hitting this issue, the networkmanager logs show:

NetworkManager[773]: <info> [1488932351.8820] manager: wake requested (sleeping: yes enabled: yes)
NetworkManager[773]: <info> [1488932351.8821] manager: waking up...
NetworkManager[773]: <info> [1488932351.8823] device (wlp58s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
NetworkManager[773]: <info> [1488932354.2067] manager: NetworkManager state is now CONNECTED_LOCAL
NetworkManager[773]: <info> [1488932354.2946] device (wlp58s0): supplicant interface state: starting -> ready
NetworkManager[773]: <info> [1488932354.2948] device (wlp58s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]

when the issue doesn't occur, we also see:

NetworkManager[773]: <info> [1488955550.0568] device (wlp58s0): supplicant interface state: ready -> inactive
NetworkManager[773]: <info> [1488955550.0888] policy: auto-activating connection 'testAP'

but these are missing when the issue occurs!

[Benjamin Blanchard (kisdra)]

I also had the issue on a fresh Ubuntu 16.04, the applet not working properly after resuming from suspend.

But I may have something to help here. A few days ago, I didn't had the issue on a previous install, so I tried the two changes I made on that one suspend-related.

First, I enabled hibernation, but it didn't change anything, still the bug after resume.

And then, I installed tlp, basic with no modification, and it now works properly every time.

Hope that may help.

[Sergio Callegari (callegar)]

I see something similar in 16.10.
Weird enough, issuing an

iwlist wlan0 scan

seems to be enough to get the available connections again

[Shih-Yuan Lee (fourdollars)]

Does anyone encounter the same issue on Ubuntu 17.04?

[Duan Jiawei (roadtodream)]

I have encountered the same issue, I'm sure there is nothing related to the network-manager. This package is working properly and I can connect to any wifi as I with.
However i thing it's related with the wifi indicator:)
Generally this issue recovers after I relaunch the Xorg.

[Jamie Strandboge (jdstrand)]

Is this still an issue with 1.2.6-0ubuntu0.16.04.3 in 16.04? I see that Ken applied the patch I identified in https://bugzilla.gnome.org/show_bug.cgi?id=767317 to fix https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1641889, which references a different upstream bug.

[Douglas Silva (o-alquimista)]

Using ath9k driver: no issues

My netbook running iwlwifi driver still has this bug. It's in Ubuntu, because I'm running Debian Stretch just fine there.

[Shih-Yuan Lee (fourdollars)]

https://packages.debian.org/stretch/network-manager has contained those fixes.

Could someone help to test https://launchpad.net/~happyaron/+archive/ubuntu/nm-oem/+packages if it can fix this bug?

[ComputersHowtoGeek (computershowtopro)]

I'm posting this here merely because another bug page on launchpad says that that thread,is actually a duplicate of this one, even though it seems it's not.
I'm on Peppermint, which is still ubuntu under the hood, all else works fine, except from time to time, with no explanation, regardless of whether waking up from a sleep session , or a full reboot, sometimes nm-applet loads fine, sometimes it doesn't, and displays this as an error:
(nm-applet:2962): nm-applet-CRITICAL **: get_menu_item_for_ap: assertion 'dup_data.hash != NULL' failed

The laptop is dell i1720 - if it at all matters - and it's a Peppermint 7, with all currently known secure updates applied, and Xenial "under the hood".

Can anyone please provide a fix, even an unofficial one ?
Thank you

[Shih-Yuan Lee (fourdollars)]

What's the output of `nmcli d` when the problem happens?

[Mark (mago90)]

I am still having this issue on Lubuntu 16.04.3, could it be possibly related to another bug I opened: #1719731? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719731

[Yuriy Vidineev (adeptg)]

I still have this bug on Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi
Both with:

ii network-manager 1.2.6-0ubuntu0.16.04.2 amd64 network management framework (daemon and userspace tools)
ii network-manager-gnome 1.2.6-0ubuntu0.16.04.4 amd64 network management framework (GNOME frontend)

It's 100% reproducible. If there are any patches/proposed versions - I can help with testing

[Kai-Heng Feng (kaihengfeng)]

Yuriy, please file a separate bug. Run `ubuntu-bug linux`.

[Yuriy Vidineev (adeptg)]

It's not seems as linux bug because there is how I'm fixing it:

killall nm-applet && nm-applet &

[Yuriy Vidineev (adeptg)]

I've filed separate bug
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812

[Yuriy Vidineev (adeptg)]

Here is how nm-applet looks after restart (killall nm-applet && nm-applet &)

[Shih-Yuan Lee (fourdollars)]

It can not prove if it is a linux kernel bug or not even when you can recover it from the UI.

[Yuriy Vidineev (adeptg)]

Sure thing. But 2 more points that maake me believe it's user space bug:

1. nmcli dev shows correct information (I believe under the hood it uses the same syscalls as nm-applet)
2. I have this bug on a wide range of kernels from 4.4 to 4.15 We completely the same behaviour. On 2 laptops with different wi-fi adapters (ath10k and iwlwifi kernel modules)