Networkmanager 1.0.12-1 -> no Wireless connection

dank · 2016-04-30 17:08:56

Hi,
After upgrading networkmanager to 1.2.0-3, NetworkManager started treating my wireless device wlp2s0 as a wired Ethernet connection at boot.

Stopping and restarting the NetworkManager service fixed it until the next boot.

I asked on networkmanger-list@gnome.org, and Thomas Haller said this was a known bug which has already been fixed upstream:

https://cgit.freedesktop.org/NetworkMan … 559b93d034

Last edited by dank (2016-04-30 17:11:21)

apastuszak · 2016-05-01 00:09:25

On 1.10 I stay till the new version is released.

butler360 · 2016-05-02 00:23:55

Restarting the service works for me.

slashrsm · 2016-05-02 19:15:09

Same here. Have to do it after every reboot.

If I understand correctly we need to wait for new version to be released?

Last edited by slashrsm (2016-05-02 19:15:57)

jasonwryan · 2016-05-07 21:14:37

Stickying until this passes through...

epimenidecretese · 2016-05-11 08:33:05

butler360 wrote:

Restarting the service works for me.

Same here on dell xps 12 mlk.

bonsairoot · 2016-05-11 15:24:50

Removed networkmanager,the applet and openconnect from ignore after I saw the new update ( ->1.2.2-1). So far the issue described here (with v1.2.0-3) seems to be resolved in the new version.

netadmin · 2016-05-12 12:38:36

Confirmed this is solved with 1.2.2-1

OssiL · 2016-05-14 15:58:47

1.2.2-1 doesn't solve for me, I need manually restart it after boot.

I have USB wifi adapter.

1.0.10 fails with:

touko 14 18:21:24 arssi systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
touko 14 18:21:24 arssi NetworkManager[309]: <error> [1463239284.301958] [platform/wifi/wifi-utils-wext.c:496] wext_get_range(): (wlan0): couldn't get driver range inf
touko 14 18:21:24 arssi kernel: NetworkManager[309]: segfault at 8 ip 00000000004ca116 sp 00007ffc593e9158 error 4 in NetworkManager[400000+1c5000]
touko 14 18:21:24 arssi systemd[369]: Starting D-Bus User Message Bus Socket.
touko 14 18:21:24 arssi NetworkManager[309]: <info> (wlan0): driver WEXT range request failed
touko 14 18:21:24 arssi NetworkManager[309]: (NetworkManager:309): GLib-GObject-CRITICAL **: object NMDeviceWifi 0x26a3880 finalized while still in-construction
touko 14 18:21:24 arssi NetworkManager[309]: (NetworkManager:309): GLib-GObject-CRITICAL **: Custom constructor for class NMDeviceWifi returned NULL (which is invalid)
touko 14 18:21:24 arssi systemd[369]: Reached target Timers.
touko 14 18:21:24 arssi NetworkManager[309]: <warn> (wlan0): failed to initialize WiFi driver

But 1.0.10 restarts itself automatically since the core is dumped (see below):

touko 14 18:08:44 arssi systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV
touko 14 18:08:44 arssi systemd[1]: NetworkManager.service: Unit entered failed state.
touko 14 18:08:44 arssi systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
touko 14 18:08:44 arssi systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart.
touko 14 18:08:44 arssi systemd[1]: Stopped Network Manager.
touko 14 18:08:44 arssi systemd[1]: Starting Network Manager...
touko 14 18:08:44 arssi NetworkManager[399]: <info> NetworkManager (version 1.0.10) is starting...

So, for some reason core is dumped for 1.0.10:

touko 14 18:21:24 arssi systemd-coredump[381]: Process 309 (NetworkManager) of user 0 dumped core.

Stack trace of thread 309:
#0 0x00000000004ca116 n/a (NetworkManager)
#1 0x00000000004ca20e n/a (NetworkManager)
#2 0x00007f25d1f0bc8a g_main_context_dispatch (libglib-2.0.so.0)
#3 0x00007f25d1f0c040 n/a (libglib-2.0.so.0)
#4 0x00007f25d1f0c362 g_main_loop_run (libglib-2.0.so.0)
#5 0x0000000000436474 main (NetworkManager)
#6 0x00007f25d1924741 __libc_start_main (libc.so.6)
#7 0x0000000000436b39 _start (NetworkManager)

Stack trace of thread 334:
#0 0x00007f25d19e268d poll (libc.so.6)
#1 0x00007f25d1f0bfd6 n/a (libglib-2.0.so.0)
#2 0x00007f25d1f0c0ec g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f25d1f0c131 n/a (libglib-2.0.so.0)
#4 0x00007f25d1f322b5 n/a (libglib-2.0.so.0)
#5 0x00007f25d1cac474 start_thread (libpthread.so.0)
#6 0x00007f25d19eb69d __clone (libc.so.6)

Stack trace of thread 340:
#0 0x00007f25d19e7229 syscall (libc.so.6)
#1 0x00007f25d1f502aa g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007f25d1ee0a19 n/a (libglib-2.0.so.0)
#3 0x00007f25d1f32c86 n/a (libglib-2.0.so.0)
#4 0x00007f25d1f322b5 n/a (libglib-2.0.so.0)
#5 0x00007f25d1cac474 start_thread (libpthread.so.0)
#6 0x00007f25d19eb69d __clone (libc.so.6)

Stack trace of thread 343:
#0 0x00007f25d19e268d poll (libc.so.6)
#1 0x00007f25d1f0bfd6 n/a (libglib-2.0.so.0)
#2 0x00007f25d1f0c362 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f25d2507726 n/a (libgio-2.0.so.0)
#4 0x00007f25d1f322b5 n/a (libglib-2.0.so.0)
#5 0x00007f25d1cac474 start_thread (libpthread.so.0)
#6 0x00007f25d19eb69d __clone (libc.so.6)

Stack trace of thread 354:
#0 0x00007f25d19e7229 syscall (libc.so.6)
#1 0x00007f25d1f502aa g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007f25d1ee0a19 n/a (libglib-2.0.so.0)
#3 0x00007f25d1f32c86 n/a (libglib-2.0.so.0)
#4 0x00007f25d1f322b5 n/a (libglib-2.0.so.0)
#5 0x00007f25d1cac474 start_thread (libpthread.so.0)
#6 0x00007f25d19eb69d __clone (libc.so.6)

And 1.2.2 just gets error:

touko 14 18:43:07 arssi NetworkManager[326]: <error> [1463240587.3371] (wlan0): couldn't get driver range information (19).
touko 14 18:43:07 arssi NetworkManager[326]: <info> [1463240587.3371] (wlan0): driver WEXT range request failed
touko 14 18:43:07 arssi NetworkManager[326]: <warn> [1463240587.3371] (wlan0) failed to initialize Wi-Fi driver for ifindex 3
touko 14 18:43:07 arssi NetworkManager[326]: <warn> [1463240587.3371] manager: wlan0: factory failed to create device: Device factory NMWifiFactory failed to cr
touko 14 18:43:12 arssi NetworkManager[326]: <info> [1463240592.1540] manager: startup complete

So, apparently systemd thinks that all is good and there is no need to automatically restart - and thus the more broken version works better for me. LOL.

wilberfan · 2016-05-15 02:16:41

netmanager 1.2.2-1 still has the no-wireless-connection issue for me. Restarting the service did not change anything. Reverting to 1.2.0-3 restores wifi connection.

Last edited by wilberfan (2016-06-04 22:30:09)

fahrgast · 2016-05-19 08:43:04

I confirm that 1.2.2-1 solved the problem for me too.

ali_molaei · 2016-06-04 10:08:20

same problem
downgrading to 1.0.12-1 solved the problem

qwertypoke · 2016-06-06 20:35:49

Ralink Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
Driver from AUR package rt3290sta-dkms 2.6.0.0-5

On my configuration 1.2.2-1 does not show an option (NetworkManager applet) to enable/disable wifi or an option to connect to any Wifi network.
Downgrading to 1.0.10-2 restores correct functionality.

Status information of the service in both situations: (The warning about 30-nfs.sh failed is not relevant.)
1.2.2-1

# systemctl status NetworkManager.service
kesä 06 23:07:47 orava NetworkManager[368]: <info>  [1465243667.5712] manager: (enp3s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/0)
kesä 06 23:07:47 orava NetworkManager[368]: <info>  [1465243667.5757] device (enp3s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
kesä 06 23:07:47 orava NetworkManager[368]: <info>  [1465243667.6120] (enp2s0f0): driver does not support SSID scans (scan_capa 0x00).
kesä 06 23:07:47 orava NetworkManager[368]: <info>  [1465243667.6120] (enp2s0f0): using WEXT for WiFi device control
kesä 06 23:07:47 orava NetworkManager[368]: <warn>  [1465243667.6120] (enp2s0f0): error 100 getting card mode
kesä 06 23:07:47 orava NetworkManager[368]: <info>  [1465243667.6124] device (lo): link connected
kesä 06 23:07:47 orava NetworkManager[368]: <info>  [1465243667.6137] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
kesä 06 23:07:47 orava NetworkManager[368]: <info>  [1465243667.6323] ModemManager available in the bus
kesä 06 23:07:47 orava NetworkManager[368]: <warn>  [1465243667.8389] dispatcher: (1) 30-nfs.sh failed (failed): Script '/etc/NetworkManager/dispatcher.d/30-nfs.sh' exited with error status 32.
kesä 06 23:07:53 orava NetworkManager[368]: <info>  [1465243673.1435] manager: startup complete

1.0.10-2

# systemctl status NetworkManager.service
kesä 06 23:13:59 orava NetworkManager[1441]: <info>  (enp2s0f0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
kesä 06 23:13:59 orava NetworkManager[1441]: <info>  (enp2s0f0): device state change: secondaries -> activated (reason 'none') [90 100 0]
kesä 06 23:13:59 orava NetworkManager[1441]: <info>  NetworkManager state is now CONNECTED_LOCAL
kesä 06 23:13:59 orava dhclient[1452]: bound to 192.168.1.24 -- renewal in 37121 seconds.
kesä 06 23:13:59 orava NetworkManager[1441]: <info>  NetworkManager state is now CONNECTED_GLOBAL
kesä 06 23:13:59 orava NetworkManager[1441]: <info>  Policy set 'dlink' (enp2s0f0) as default for IPv4 routing and DNS.
kesä 06 23:13:59 orava NetworkManager[1441]: <info>  Writing DNS information to /usr/bin/resolvconf
kesä 06 23:14:00 orava NetworkManager[1441]: <info>  (enp2s0f0): Activation: successful, device activated.
kesä 06 23:14:00 orava NetworkManager[1441]: <warn>  (2) 30-nfs.sh failed (failed): Script '/etc/NetworkManager/dispatcher.d/30-nfs.sh' exited with error status 32.
kesä 06 23:14:03 orava NetworkManager[1441]: <info>  startup complete

TallJimbo · 2016-06-14 16:35:10

My problem appears not to be the same as that of most other posts here, but it's solved and it matches the thread title, so I'll post in case it's useful for others: I discovered after a new install (just switched from Ubuntu) with the latest NetworkManager that I couldn't get DHCP working on wired networks under NetworkManager (or when running dhcpcd manually). Installing dhclient and setting

dhcp=dhclient

in /etc/NetworkManager/NetworkManager.conf solved the problem. I still don't understand why dhcpcd wasn't working, but I'm happily up and running now.

saoded · 2016-06-14 20:59:27

wilberfan wrote:

netmanager 1.2.2-1 still has the no-wireless-connection issue for me. Restarting the service did not change anything. Reverting to 1.2.0-3 restores wifi connection.

I suspect I have the same problem as you had (Worked fine before the last change). how do I get the 1.2.0-3 version (it's not in my /var/cache/pacman/pkg directory)?
Sorry if it's a noob question, I really don't know and I tried googling but didn't find anything useful

WorMzy · 2016-06-14 22:24:54

See post #13..

wilberfan · 2016-07-11 03:06:37

Just tried upgrading to networkmanager 1.2.4-1. Still won't make a connection to wifi properly. :-( Reverted back to 1.2.0-3 (which does connect properly).

wilberfan · 2016-08-24 18:58:54

wilberfan wrote:

Just tried upgrading to networkmanager 1.2.4-1. Still won't make a connection to wifi properly. :-( Reverted back to 1.2.0-3 (which does connect properly).

The last 2 or 3 versions of NetworkManager have been unable to make a wireless connection for me. I just tried v1.2.5dev+5+g99e34d7-1, but still no connection. Reverting to a previous version is the only solution I've found. Version 1.2.0-3 is the last one that's worked properly for me.

Anyone else having this issue? Any suggestions on what else I could try?

tazee · 2016-08-24 20:50:33

wilberfan wrote:

wilberfan wrote:
Just tried upgrading to networkmanager 1.2.4-1. Still won't make a connection to wifi properly. :-( Reverted back to 1.2.0-3 (which does connect properly).
The last 2 or 3 versions of NetworkManager have been unable to make a wireless connection for me. I just tried v1.2.5dev+5+g99e34d7-1, but still no connection. Reverting to a previous version is the only solution I've found. Version 1.2.0-3 is the last one that's worked properly for me.
Anyone else having this issue? Any suggestions on what else I could try?

I too am having this issue. What should we do? Wait patiently till it is fixed?

Excubia · 2016-08-28 21:29:48

I started to have this problem with version 1.4.0-1

blaatenator · 2016-08-29 11:32:48

Here too, networkmanager worked flawless with 1.2.2-2. After update to 1.4.0-1 it failed. Netctl (wifi-menu) works fine. The hardware is a Dell XPS-13 (2016 edition) with the Broadcom Corporation BCM4350 802.11ac adapter.
nmtui gives: Could not activate the connection: Active connection removed before it was initialized. Journalctl -xe gives:

(btw: the error on IPv6 is expected, it is disabled on my system)

Aug 29 13:25:37 hostname NetworkManager[1815]: <info>  [1472469937.9060] device (wlp58s0): Activation: starting connection '<ssid>' (<essid>
Aug 29 13:25:37 hostname NetworkManager[1815]: <info>  [1472469937.9063] audit: op="connection-activate" uuid="<essid>a25f1c" name="<ssid>" 
Aug 29 13:25:37 hostname NetworkManager[1815]: <info>  [1472469937.9066] device (wlp58s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug 29 13:25:37 hostname NetworkManager[1815]: <info>  [1472469937.9068] manager: NetworkManager state is now CONNECTING
Aug 29 13:25:38 hostname NetworkManager[1815]: <warn>  [1472469938.4103] device (wlp58s0): set-hw-addr: new MAC address 30:52:CB:80:D6:55 not successfully set to set-cloned (per
Aug 29 13:25:38 hostname NetworkManager[1815]: <info>  [1472469938.4129] device (wlp58s0): state change: prepare -> failed (reason 'none') [40 120 0]
Aug 29 13:25:38 hostname NetworkManager[1815]: <info>  [1472469938.4134] manager: NetworkManager state is now DISCONNECTED
Aug 29 13:25:38 hostname NetworkManager[1815]: <warn>  [1472469938.4144] device (wlp58s0): Activation: failed for connection '<ssid>'
Aug 29 13:25:38 hostname kernel: IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
Aug 29 13:25:38 hostname NetworkManager[1815]: <info>  [1472469938.4236] device (wlp58s0): state change: failed -> disconnected (reason 'none') [120 30 0]

Just confirmed: downgrading package networkmanager to 1.2.4-1 brings it back to working state again.

Last edited by blaatenator (2016-08-29 11:45:59)

kang · 2016-08-29 21:58:57

Same as blaatenator - same hardware same problem.
Network manager tries to set your wifi mac address to a random mac and the driver (brcmfmac) doesn't work properly when you do that.
Normally network manager should not do that.

Also that's how you see it:

Aug 29 13:25:38 hostname NetworkManager[1815]: <warn>  [1472469938.4103] device (wlp58s0): set-hw-addr: new MAC address 30:52:CB:80:D6:55 not successfully set to set-cloned (per

if you fresh start or reload brcmfmac and you check your mac ("ip link") you'll see a different one.

There is no option that will prevent Network manager to do this - its buggy right now, it does it regardless of options. Gah ;-)

networkmanager-1.4.1dev+9+ga3fd485-1-x86_64.pkg.tar.xz

is affected.

Last edited by kang (2016-08-29 22:01:15)

txomon · 2016-08-30 23:27:37

Related nm ticket https://bugzilla.gnome.org/show_bug.cgi?id=770504

TL;DR: It is something wrong with mac randomization for scans. Solution, downgrade or configure:

[device]
wifi.scan-rand-mac-address=no

Last edited by txomon (2016-08-30 23:28:49)

wilberfan · 2016-08-31 01:51:48

I just installed NetworkManager 1.4.1dev+9+ga3fd485-1. I still had the no-wifi-connection issue--until I swapped out my existing /etc/NetworkManager/NetworkManager.conf with the NetworkManager.conf.pacnew that arrived with the new version. When I made that swap, and restarted NetworkManager service, my wifi connection came up right away.

My original .conf was:

[main]
plugins=keyfile
dns=dnsmasq
dhcp=dhclient

The new one is:
[main]
plugins=keyfile
dns=default

## HTTP-based connectivity check
#[connectivity]
#uri=http://nmcheck.gnome.org/check_network_status.txt
#interval=100

Last edited by wilberfan (2016-08-31 02:05:57)

ali_molaei · 2016-08-31 07:39:49

My Version - Problem History
1.0.12-1 NoProblem
renge between 1.0.12 and 1.2.5 Problem
1.2.5dev NoProblem
1.4.0-1 Problem
1.4.1dev NoProblem

/etc/NetworkManager/NetworkManager.conf

[main]
plugins=keyfile
dns=default

## HTTP-based connectivity check
#[connectivity]
#uri=http://nmcheck.gnome.org/check_network_status.txt
#interval=100

Arch Linux

#26 2016-04-30 17:08:56

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#27 2016-05-01 00:09:25

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#28 2016-05-02 00:23:55

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#29 2016-05-02 19:15:09

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#30 2016-05-07 21:14:37

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#31 2016-05-11 08:33:05

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#32 2016-05-11 15:24:50

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#33 2016-05-12 12:38:36

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#34 2016-05-14 15:58:47

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#35 2016-05-15 02:16:41

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#36 2016-05-19 08:43:04

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#37 2016-06-04 10:08:20

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#38 2016-06-06 20:35:49

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#39 2016-06-14 16:35:10

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#40 2016-06-14 20:59:27

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#41 2016-06-14 22:24:54

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#42 2016-07-11 03:06:37

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#43 2016-08-24 18:58:54

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#44 2016-08-24 20:50:33

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#45 2016-08-28 21:29:48

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#46 2016-08-29 11:32:48

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#47 2016-08-29 21:58:57

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#48 2016-08-30 23:27:37

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#49 2016-08-31 01:51:48

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#50 2016-08-31 07:39:49

Re: Networkmanager 1.0.12-1 -> no Wireless connection

Board footer