[SOLVED] NetworkManager "stopped working" as of 1.4.0

hobarrera · 2016-08-27 03:58:36

My wireless network stopped working, almost suddenly, after a power cycle due to depleted battery today.

When connecting to a saved connection, via NetworkManager, I get "Active connection removed before it was initialized".

If I delete the connection and try to connect, NM shows this message : "Failed to add/activate connection. The access point /org/freedesktop/NetworkManager/AccessPoint/1 was not in the scan list".

I tried using wpa_supplicant directy, but it still fails, so I don't think it's anything NM specific. I also connected to the network with a USB wireless adapter, further confirming that NM is probably not the problem.

I've no idea what else to try, or how to further pinpoint the issue here.

[UPDATE]

I have tracked the issue to NetworkManager 1.4.0. I'm copy-pasting what I posted in the broadcom-wl-dkms driver page:

I downgraded networkmanager to the previous version and my network works again, so:

* The issue is some interaction between networkmanager and wl. NM works fine with other drivers.
* Even if you skip NM and use the cli, it seems that it somehow gets in the way and breaks things.

I'm currently back to networkmanger-1.2.5dev+5+g99e34d7.

Last edited by hobarrera (2016-08-29 00:30:01)

loafer · 2016-08-27 06:41:08

This issue seems to be well known (there's also an open bug report):

https://bbs.archlinux.org/viewtopic.php?id=210868&p

hobarrera · 2016-08-27 06:48:10

loafer wrote:

This issue seems to be well known (there's also an open bug report):
https://bbs.archlinux.org/viewtopic.php?id=210868&p

That looks like an entirely different bug:

* Different version of NM (my issue in on NM>=1.4.0, that's 1.0.2).
* My issue is ONLY reproducible with wl. That's using another driver, apparently.

ziggi · 2016-08-28 05:57:38

Have the same problem.

skyxxzc · 2016-08-28 11:26:50

Me too. Downgrading to networkmanager 1.2.5dev+5+g99e34d7-1 solved the problem.

Aug 28 18:05:59 skyxxzc NetworkManager[421]: <info> [1472378759.3655] policy: auto-activating connection 'Hightree'
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <info> [1472378759.3687] device (wlp3s0): Activation: starting connection 'Hightree'
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <info> [1472378759.3696] device (wlp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <error> [1472378759.3714] platform-linux: do-change-link[3]: failure changing link: failure 23 (系统中打开的文件过多) //Too many open files
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <warn> [1472378759.3720] device (wlp3s0): set-hw-addr: failed to set-cloned MAC address to F8:xx:xx:xx:xx:xx (permanent) (unspecified)
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <info> [1472378759.3728] device (wlp3s0): state change: prepare -> failed (reason 'none') [40 120 0]
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <info> [1472378759.3735] policy: disabling autoconnect for connection 'Hightree'.
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <warn> [1472378759.3743] device (wlp3s0): Activation: failed for connection 'Hightree'
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <info> [1472378759.3760] device (wlp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <error> [1472378759.4445] platform-linux: do-change-link[3]: failure changing link: failure 23 (系统中打开的文件过多)
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <warn> [1472378759.4445] device (wlp3s0): set-hw-addr: failed to set MAC address to F8:xx:xx:xx:xx:xx (scanning) (unspecified)
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <info> [1472378759.4470] device (wlp3s0): supplicant interface state: inactive -> disconnected
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <info> [1472378759.4525] device (wlp3s0): supplicant interface state: disconnected -> inactive
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <info> [1472378759.4933] device (wlp3s0): supplicant interface state: inactive -> disconnected
Aug 28 18:05:59 skyxxzc NetworkManager[421]: <info> [1472378759.5150] device (wlp3s0): supplicant interface state: disconnected -> inactive

And nm-applet showed the same error message with OP.

Last edited by skyxxzc (2016-08-28 12:08:55)

Dante777 · 2016-08-28 12:46:06

Same issue here guys, with NM and wl driver.
Solved by downgrading NM package.

loafer · 2016-08-28 12:46:32

Are you using the same driver as the OP?

phantohaut · 2016-08-28 15:17:22

Same issue here with wl driver and Networkmanager 1.4.0. Solved by downgrading.

jethronsun7 · 2016-08-28 17:37:59

Thanks very much!!

I have experienced this problem and downgrading saved my ass.

My system:
Arch on Mac + gnome + awesome vm.

For anyone who is not familiar with downgrading pkg: https://wiki.archlinux.org/index.php/Do … g_packages

loafer · 2016-08-28 19:30:26

Has anyone opened a bug report or appended to an existing one? I do not use NM but there seems to be a lot of people with an issue.

hoerbert · 2016-08-28 19:37:59

To summarize:

There is an upstream-bug at network-manager. It is stated, that the original bug lies in the driver, but that network-manager could and should work around this. See https://bugzilla.gnome.org/show_bug.cgi?id=770456
There already is a proposed patch to fix this: https://cgit.freedesktop.org/NetworkMan … 7e7e5ff682
For the meantime there is a proposed word-around to make the new network-manager work with the wl driver. See https://bugzilla.gnome.org/show_bug.cgi?id=770456#c14

If the patch is accepted we should consider adding it to our current package.

loqs · 2016-08-28 19:38:05

loafer wrote:

Has anyone opened a bug report or appended to an existing one? I do not use NM but there seems to be a lot of people with an issue.

https://bugs.archlinux.org/task/50546
https://bugs.archlinux.org/task/50546#comment150466
https://cgit.freedesktop.org/NetworkMan … 7e7e5ff682
Edit: Ah hoerbert already posted it

Last edited by loqs (2016-08-28 19:39:50)

Jujstme · 2016-08-28 19:38:38

It's a bug that has been fixed upstream a couple of hours ago: https://bugzilla.gnome.org/show_bug.cgi?id=770456
The next update to nm will probably address this issue.

There is also a workaround that involves disabling MAC address randomization during wifi network scanning. Just added this in the wiki: https://wiki.archlinux.org/index.php/Br … ager_1.4.0

EDIT: I got anticipated by others. My bad

Last edited by Jujstme (2016-08-28 19:39:13)

hobarrera · 2016-08-28 19:48:39

Apparently, the issue is not the driver; someone has posted upstream that using the open FLOSS driver yields the same results. I cannot confirm this since my hardware only supports the propietary driver, regrettably, but it may be possible that it's actually a hardware issue. (or maybe the FLOSS driver also reproduces the same bug).

Excubia · 2016-08-28 23:50:08

Same problem, with the same hardware: Macbook Air.

jasonwryan · 2016-08-29 00:06:10

Excubia: stop power posting in all these NM threads. https://wiki.archlinux.org/index.php/Co … mpty_posts

hobarrera · 2016-08-29 00:17:27

Excubia wrote:

Same problem, with the same hardware: Macbook Air.

Yeah, same here. You also probably have a BCM4360 too.

Jujstme · 2016-08-29 00:26:57

hobarrera wrote:

Yeah, same here. You also probably have a BCM4360 too.

Did you try the workaround in the wiki? It works in my BCM4360 and seems to be working for others, too.

hobarrera · 2016-08-29 00:29:38

I worked around the issue by downgrading, I have not tried other workarounds.
Several different workarounds have been proposed after my initial report:

https://aur.archlinux.org/packages/broadcom-wl-dkms/

I'll make this solved, since upstream is already dealing with it and we have enough workarounds for now.

lovetide · 2016-09-07 16:22:43

Thanks for the workaround information!
Just let you know, same thing happened in Debian unstable too (NetworkManager-1.4.0 + broadcom-sta-dkms), and downgrading works too.

vniku · 2016-12-29 14:23:59

I solved the problem by using the "Connect to Hidden WiFi network ..." prompt and in it typing the network name myself.. That is, ignoring all the scanning for it, as the problem seem to be associated with scanning ("reject scan trigger since one is already pending").

I was getting error messages like the one mentioned below, and I could not connect. After "manually" supplying the network ESSID, I could connect. Afterwards, NetworkManager app saves the connection information as `<ESSID> 1', and by clicking on it, I can connect to the network.

NetworkManager version: 1.4.4. Uptodate Arch Linux.
Extract from journalctl output:

Dec 29 18:56:27 archlinux NetworkManager[321]: <info> [1483017987.9009] device (wlp8s0): set-hw-addr: set MAC address to 0A:75:C8:3B:C
...
Dec 29 18:56:28 archlinux kernel: IPv6: ADDRCONF(NETDEV_UP): wlp8s0: link is not ready
Dec 29 18:56:28 archlinux NetworkManager[321]: <info> [1483017988.2367] device (wlp8s0): supplicant interface state: inactive -> disab
Dec 29 18:56:28 archlinux NetworkManager[321]: <info> [1483017988.2743] device (wlp8s0): supplicant interface state: disabled -> inact
Dec 29 18:56:28 archlinux wpa_supplicant[340]: wlp8s0: Reject scan trigger since one is already pending
...
Dec 29 19:01:43 archlinux NetworkManager[321]: <info> [1483018303.9025] device (wlp8s0): set-hw-addr: set MAC address to B2:A5:79:45:A
...

Last edited by vniku (2016-12-29 14:27:14)

Arch Linux

#1 2016-08-27 03:58:36

[SOLVED] NetworkManager "stopped working" as of 1.4.0

#2 2016-08-27 06:41:08

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#3 2016-08-27 06:48:10

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#4 2016-08-28 05:57:38

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#5 2016-08-28 11:26:50

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#6 2016-08-28 12:46:06

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#7 2016-08-28 12:46:32

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#8 2016-08-28 15:17:22

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#9 2016-08-28 17:37:59

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#10 2016-08-28 19:30:26

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#11 2016-08-28 19:37:59

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#12 2016-08-28 19:38:05

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#13 2016-08-28 19:38:38

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#14 2016-08-28 19:48:39

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#15 2016-08-28 23:50:08

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#16 2016-08-29 00:06:10

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#17 2016-08-29 00:17:27

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#18 2016-08-29 00:26:57

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#19 2016-08-29 00:29:38

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#20 2016-09-07 16:22:43

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

#21 2016-12-29 14:23:59

Re: [SOLVED] NetworkManager "stopped working" as of 1.4.0

Board footer