http://bugzilla.opensuse.org/show_bug.cgi?id=1167319 Bug ID: 1167319 Summary: wlan fails to start on boot after wpa_supplicant upgraded to 2.6-lp151.5.3.1-x86_64 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs@suse.de Reporter: jhtaylor20@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- My wlan0 no longer starts automatically on boot after the patch that upgraded wpa_supplicant to 2.6-lp151.5.3.1-x86_64. After I log in I can start it with "wicked ifup wlan0". If I downgrade wpa_supplicant back down to 2.6-lp151.4.4.x86_64 my wlan0 starts on boot a before. The following is logged on boot: <code> Mar 21 09:00:18 HP-Linux dbus-daemon[1012]: [system] Failed to activate service 'fi.epitest.hostap.WPASupplicant': timed out (service_start_timeout=25000ms) Mar 21 09:00:18 HP-Linux wickedd[1230]: ni_wpa_interface_bind(wlan0): Operation not permitted Mar 21 09:00:18 HP-Linux wickedd[1230]: wpa_supplicant doesn't know interface wlan0 Mar 21 09:00:18 HP-Linux wickedd-nanny[1236]: device wlan0: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure Mar 21 09:00:18 HP-Linux wickedd-nanny[1236]: wlan0: failed to bring up device, still continuing Mar 21 09:00:23 HP-Linux wicked[1237]: lo up Mar 21 09:00:23 HP-Linux wicked[1237]: wlan0 device-not-running Mar 21 09:00:23 HP-Linux wicked[1237]: eth0 no-device Mar 21 09:00:23 HP-Linux wicked[1237]: wlan0-save no-device Mar 21 09:00:23 HP-Linux systemd[1]: Started wicked managed network interfaces. Mar 21 09:00:23 HP-Linux systemd[1]: Reached target Network. Mar 21 09:00:23 HP-Linux systemd[1]: Starting OpenSSH Daemon... Mar 21 09:00:23 HP-Linux systemd[1]: Starting WPA Supplicant daemon... Mar 21 09:00:23 HP-Linux systemd[1]: Started Backup of /etc/sysconfig. </code> The patch that installed the failing wpa_supplicant version references bug 1165266 -- You are receiving this mail because: You are on the CC list for the bug.