Is caused by missing wpa_supplicant.
Alternate workaround is to start it manually;
systemctl start wpa_supplicant
After this, wireless can be used. The reason reboot worked was that it
did the same thing.
According to syslog, when the host name changes from oem-INVALID to user
preference captured by oem-config, wpa_supplicant is stopped by systemd,
but does not start again.
What systemd thinks of wpa_supplicant at the time of the problem:
# systemctl status wpa_supplicant
● wpa_supplicant.service - WPA supplicant
Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; disabled; vendor
preset: enabled)
Active: inactive (dead)
Sep 28 13:18:51 oem-INVALID systemd[1]: Starting WPA supplicant...
Sep 28 13:18:51 oem-INVALID systemd[1]: Started WPA supplicant.
Sep 28 13:18:51 oem-INVALID wpa_supplicant[781]: Successfully initialized
wpa_supplicant
Sep 28 13:18:51 oem-INVALID wpa_supplicant[781]: dbus:
wpa_dbus_get_object_properties: failed to get object properties: (none) none
Sep 28 13:18:51 oem-INVALID wpa_supplicant[781]: dbus: Failed to construct
signal
Sep 28 13:21:44 olpc systemd[1]: Stopping WPA supplicant...
Sep 28 13:21:44 olpc wpa_supplicant[781]: nl80211: deinit ifname=wlp2s0
disabled_11b_rates=0
Sep 28 13:21:45 olpc systemd[1]: Stopped WPA supplicant.
Hope that helps someone fix this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573474
Title:
ubuntu 16.04 oem config wireless
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1573474/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
