Comment # 3 on bug 967427 from Alick Gardiner

I believe I have the same or at least similar.  wpa_supplicant|2.5-73.1
prevented me from seeing access points, downgrading in yast using an ethernet
connection fixed it. logs showed this:

name@linux-2qhx:~> systemctl status NetworkManager.service -l
NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
   Active: active (running) since Sun 2016-02-21 22:42:10 GMT; 1min 5s ago
 Main PID: 812 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           ������812 /usr/sbin/NetworkManager --no-daemon                           

Feb 21 22:42:10 linux-2qhx.site NetworkManager[812]: <info> (wlp2s0): using
nl80211 for WiFi device control                                                 
Feb 21 22:42:10 linux-2qhx.site NetworkManager[812]: <info> (wlp2s0): driver
supports Access Point (AP) mode                                                 
Feb 21 22:42:10 linux-2qhx.site NetworkManager[812]: <info> (wlp2s0): new
802.11 WiFi device (driver: 'ath9k' ifindex: 3)                                 
Feb 21 22:42:10 linux-2qhx.site NetworkManager[812]: <info> (wlp2s0): exported
as /org/freedesktop/NetworkManager/Devices/2                                    
Feb 21 22:42:10 linux-2qhx.site NetworkManager[812]: <info> (wlp2s0): device
state change: unmanaged -> unavailable (reason 'managed') [10 20 2]             
Feb 21 22:42:10 linux-2qhx.site NetworkManager[812]: <info> (wlp2s0): preparing
device                                                                          
Feb 21 22:42:10 linux-2qhx.site NetworkManager[812]: <info> ModemManager
available in the bus                                                            
Feb 21 22:42:35 linux-2qhx.site NetworkManager[812]: <warn> Unexpected error
requesting supplicant properties: (4) Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.                                    
Feb 21 22:42:35 linux-2qhx.site NetworkManager[812]: <info> (wlp2s0):
supplicant interface state: starting -> init                                    
Feb 21 22:42:36 linux-2qhx.site NetworkManager[812]: <info> use BlueZ version 5