FS#61246 - [wpa_supplicant] Upgrade 1:2.6-12 -> 1:2.7-1 broke wifi connection

Attached to Project: Arch Linux
Opened by daimonion (demon) - Wednesday, 02 January 2019, 11:28 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 03 January 2019, 15:15 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:

Update from 1:2.6-12 to 1:2.7-1 broke my wifi connection. Downgrade to previous package version made it work again.

Wireless card: 01:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)

Log:

```
јан 02 11:38:26 daimonion-lap NetworkManager[423]: <info> [1546425506.6396] policy: auto-activating connection 'HAARP' (89ce294a-8a83-47d2-b85d-4b91e8c78b33)
јан 02 11:38:26 daimonion-lap NetworkManager[423]: <info> [1546425506.6404] device (wlp1s0): Activation: starting connection 'HAARP' (89ce294a-8a83-47d2-b85d-4b91e8c78b33)
јан 02 11:38:26 daimonion-lap NetworkManager[423]: <info> [1546425506.6405] device (wlp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
јан 02 11:38:26 daimonion-lap NetworkManager[423]: <info> [1546425506.6408] manager: NetworkManager state is now CONNECTING

јан 02 11:38:26 daimonion-lap NetworkManager[423]: <info> [1546425506.6497] device (wlp1s0): set-hw-addr: reset MAC address to 30:10:B3:06:18:61 (preserve)

јан 02 11:38:26 daimonion-lap kernel: IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready

јан 02 11:38:26 daimonion-lap NetworkManager[423]: <info> [1546425506.6599] device (wlp1s0): supplicant interface state: ready -> disabled
јан 02 11:38:26 daimonion-lap NetworkManager[423]: <info> [1546425506.6600] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
јан 02 11:38:26 daimonion-lap NetworkManager[423]: <info> [1546425506.6604] device (wlp1s0): Activation: (wifi) access point 'HAARP' has security, but secrets are required.
јан 02 11:38:26 daimonion-lap NetworkManager[423]: <info> [1546425506.6604] device (wlp1s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
јан 02 11:38:26 daimonion-lap NetworkManager[423]: <warn> [1546425506.6611] device (wlp1s0): No agents were available for this request.
јан 02 11:38:26 daimonion-lap NetworkManager[423]: <info> [1546425506.6611] device (wlp1s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
јан 02 11:38:26 daimonion-lap NetworkManager[423]: <info> [1546425506.6615] manager: NetworkManager state is now DISCONNECTED
јан 02 11:38:26 daimonion-lap NetworkManager[423]: <warn> [1546425506.6620] device (wlp1s0): Activation: failed for connection 'HAARP'
јан 02 11:38:26 daimonion-lap NetworkManager[423]: <info> [1546425506.6623] device (wlp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
```
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Thursday, 03 January 2019, 15:15 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#61119 
Comment by mdraw (drawm) - Wednesday, 02 January 2019, 12:08 GMT
I have the same issue with my Thinkpad T440s (Intel Corporation Wireless 7260 (rev 6b)). Downgrading to wpa_supplicant 1:2.6-12 also fixed it for me.
Comment by Jan Johansson (jajo) - Wednesday, 02 January 2019, 18:18 GMT
I have a broadcom wifi, and the upgrade to latest version causes the wifi not to work, as described in the log above. Downgrading to 1:2.6-12 makes the wifi work without problems again.
Comment by daimonion (demon) - Wednesday, 02 January 2019, 18:44 GMT
This seems to be related to https://bugs.archlinux.org/task/61119
Comment by Tom Boshoven (TBoshoven) - Wednesday, 02 January 2019, 20:26 GMT
I'm getting the same error as in 61119. Can confirm that they're related for me. A wpa_supplicant downgrade removes the error in that ticket.
Comment by Oleg Nagornij (corner) - Thursday, 03 January 2019, 11:21 GMT
I have the same issue

WiFi card : ASUS
Driver : broadcom-wl-dkms
lspci -s 05:00.0 -v
05:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03)
Subsystem: ASUSTeK Computer Inc. BCM4360 802.11ac Wireless Network Adapter
Flags: bus master, fast devsel, latency 0, IRQ 19, NUMA node 0
Memory at fb400000 (64-bit, non-prefetchable) [size=32K]
Memory at fb200000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [48] Power Management version 3
Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [68] Vendor Specific Information: Len=44 <?>
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Device Serial Number 1c-87-00-ff-ff-00-00-00
Capabilities: [150] Power Budgeting <?>
Capabilities: [160] Virtual Channel
Capabilities: [1b0] Latency Tolerance Reporting
Capabilities: [220] Resizable BAR <?>
Kernel driver in use: wl
Kernel modules: bcma, wl

journal

Jan 03 13:10:35 desktop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
Jan 03 13:10:35 desktop NetworkManager[672]: <info> [1546513835.2108] device (wlp5s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 03 13:10:35 desktop NetworkManager[672]: <info> [1546513835.2114] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 03 13:10:35 desktop NetworkManager[672]: <info> [1546513835.2117] device (wlp5s0): Activation: (wifi) connection 'DepartDev5' has security, and secrets exist. No new secrets needed.
Jan 03 13:10:35 desktop NetworkManager[672]: <info> [1546513835.2118] Config: added 'ssid' value 'DepartDev5'
Jan 03 13:10:35 desktop NetworkManager[672]: <info> [1546513835.2118] Config: added 'scan_ssid' value '1'
Jan 03 13:10:35 desktop NetworkManager[672]: <info> [1546513835.2118] Config: added 'bgscan' value 'simple:30:-80:86400'
Jan 03 13:10:35 desktop NetworkManager[672]: <info> [1546513835.2118] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256'
Jan 03 13:10:35 desktop NetworkManager[672]: <info> [1546513835.2118] Config: added 'psk' value '<hidden>'
Jan 03 13:10:35 desktop NetworkManager[672]: <info> [1546513835.2119] Config: added 'ieee80211w' value '1'
Jan 03 13:10:35 desktop NetworkManager[672]: <info> [1546513835.2556] device (wlp5s0): supplicant interface state: inactive -> disconnected
Jan 03 13:10:35 desktop NetworkManager[672]: <info> [1546513835.2618] device (wlp5s0): supplicant interface state: disconnected -> inactive
Jan 03 13:10:35 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:36 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:37 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:38 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:39 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:40 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:41 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:42 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:43 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:44 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:45 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:46 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:47 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:48 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:49 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:50 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:51 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:52 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:53 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:54 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:55 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:56 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:57 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:58 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:10:59 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:11:00 desktop wpa_supplicant[1002]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jan 03 13:11:00 desktop NetworkManager[672]: <warn> [1546513860.4875] device (wlp5s0): Activation: (wifi) association took too long, failing activation
Jan 03 13:11:00 desktop NetworkManager[672]: <info> [1546513860.4875] device (wlp5s0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jan 03 13:11:00 desktop NetworkManager[672]: <info> [1546513860.4881] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 03 13:11:00 desktop NetworkManager[672]: <warn> [1546513860.4890] device (wlp5s0): Activation: failed for connection 'DepartDev5'
Jan 03 13:11:00 desktop NetworkManager[672]: <info> [1546513860.4894] device (wlp5s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 03 13:11:00 desktop gnome-shell[1329]: An active wireless connection, in infrastructure mode, involves no access point?
Jan 03 13:11:00 desktop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
Jan 03 13:11:00 desktop NetworkManager[672]: <info> [1546513860.4950] device (wlp5s0): set-hw-addr: set MAC address to BA:BC:C6:44:D8:E7 (scanning)
Jan 03 13:11:00 desktop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready

Downgraded to previous version solved this issue

Loading...