It seems this bug wasn't tracked with great enthusiasm, but I can say that NetworkManager now works on the same hardware with these updates: NetworkManager-1.0.12-4.3.1.x86_64 Di 02 Mai 2017 20:14:22 CEST NetworkManager-lang-1.0.12-4.3.1.noarch Di 02 Mai 2017 20:14:30 CEST libnm-glib4-1.0.12-4.3.1.x86_64 Di 02 Mai 2017 20:14:22 CEST libnm-util2-1.0.12-4.3.1.x86_64 Di 02 Mai 2017 20:14:12 CEST libnm0-1.0.12-4.3.1.x86_64 Di 02 Mai 2017 20:14:12 CEST typelib-1_0-NMClient-1_0-1.0.12-4.3.1.x86_64 Di 02 Mai 2017 20:14:30 CEST kernel-default-4.4.62-18.6.1.x86_64 Di 02 Mai 2017 20:12:43 CEST (maybe more; as I don't know what was fixed, I can only guess)