Your message dated Thu, 28 Dec 2017 09:34:08 +0000 with message-id <[email protected]> and subject line Bug#833507: fixed in wpa 2:2.6-14 has caused the Debian Bug report #833507, regarding broadcom fails with wpa 2.5+ to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 833507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833507 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: broadcom-sta-dkms Version: 6.30.223.271-5 Severity: important Dear Maintainer, I am reporting essentially the same issue as in the recently-closed bug #849034. After upgrading to latest version of broadcom-sta-dkms, wifi connections no longer work on my Dell Latitude E5520, running up-to-date debian sid. The problem began once I upgraded broadcom-sta-dkms to the above-stated version. Here is the output of 'lspci -v' for the wireless card: 02:00.0 Network controller: Broadcom Limited BCM43228 802.11a/b/g/n Subsystem: Dell Wireless 1530 Half-size Mini PCIe Card Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at e5300000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [58] Vendor Specific Information: Len=78 <?> Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [d0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Capabilities: [160] Device Serial Number 00-00-da-ff-ff-7c-c0-f8 Capabilities: [16c] Power Budgeting <?> Kernel driver in use: wl Kernel modules: bcma, wl Here is what appears in the NetworkManager log when attempting to connect (to SSID "TheFrogurtIsAlsoCursed", with correct passphrase): Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6204] device (wlp2s0): Activation: starting connection 'TheFrogurtIsAlsoCursed' (adf41f0e-3504-4367-9685-a7d204785857) Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6209] audit: op="connection-activate" uuid="adf41f0e-3504-4367-9685-a7d204785857" name="TheFrogurtIsAlsoCursed" pid=833 uid=1000 result="success" Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6212] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6216] manager: NetworkManager state is now CONNECTING Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6231] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6236] device (wlp2s0): Activation: (wifi) access point 'TheFrogurtIsAlsoCursed' has security, but secrets are required. Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6237] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0] Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6407] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0] Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6413] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6416] device (wlp2s0): Activation: (wifi) connection 'TheFrogurtIsAlsoCursed' has security, and secrets exist. No new secrets needed. Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6417] Config: added 'ssid' value 'TheFrogurtIsAlsoCursed' Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6417] Config: added 'scan_ssid' value '1' Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6418] Config: added 'key_mgmt' value 'WPA-PSK' Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6418] Config: added 'auth_alg' value 'OPEN' Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6418] Config: added 'psk' value '<omitted>' Jan 01 11:52:55 sid NetworkManager[453]: <info> [1483300375.6446] sup-iface[0x55aa8feea970,wlp2s0]: config: set interface ap_scan to 1 Jan 01 11:53:20 sid NetworkManager[453]: <warn> [1483300400.5283] device (wlp2s0): Activation: (wifi) association took too long, failing activation Jan 01 11:53:20 sid NetworkManager[453]: <info> [1483300400.5284] device (wlp2s0): state change: config -> failed (reason 'ssid-not-found') [50 120 53] Jan 01 11:53:20 sid NetworkManager[453]: <info> [1483300400.5291] manager: NetworkManager state is now DISCONNECTED Jan 01 11:53:20 sid NetworkManager[453]: <warn> [1483300400.5317] device (wlp2s0): Activation: failed for connection 'TheFrogurtIsAlsoCursed' Jan 01 11:53:20 sid NetworkManager[453]: <info> [1483300400.5328] device (wlp2s0): supplicant interface state: inactive -> disconnected Jan 01 11:53:20 sid NetworkManager[453]: <info> [1483300400.5352] device (wlp2s0): state change: failed -> disconnected (reason 'none') [120 30 0] Jan 01 11:53:22 sid NetworkManager[453]: <info> [1483300402.6625] device (wlp2s0): supplicant interface state: disconnected -> inactive And here is what appears in the wpa_supplicant log at the same time: Jan 01 11:52:55 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:52:56 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:52:57 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:52:58 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:52:59 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:00 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:01 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:02 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:03 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:04 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:05 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:06 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:07 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:08 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:09 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:10 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:11 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:12 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:13 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:14 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:15 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:16 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:17 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:18 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Jan 01 11:53:19 sid wpa_supplicant[552]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 In one of the responses to bug #849034, it was suggested to try adding these lines ... [device] wifi.scan-rand-mac-address=no ... to /etc/NetworkManager/NetworkManager.conf, and then reboot. Unfortunately, this did not solve the problem for me. I wanted to try downgrading to the previous version of the package, but it appears that the sid version recently migrated to stretch, and so I can only find the jessie and jessie-backports versions. Anyway, thank you for your time. Steven M. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages broadcom-sta-dkms depends on: ii dkms 2.3-2 Versions of packages broadcom-sta-dkms recommends: ii wireless-tools 30~pre9-12 broadcom-sta-dkms suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: wpa Source-Version: 2:2.6-14 We believe that the bug you reported is fixed in the latest version of wpa, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Shadura <[email protected]> (supplier of updated wpa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Thu, 28 Dec 2017 09:51:29 +0100 Source: wpa Binary: hostapd wpagui wpasupplicant wpasupplicant-udeb Architecture: source Version: 2:2.6-14 Distribution: unstable Urgency: medium Maintainer: Debian wpasupplicant Maintainers <[email protected]> Changed-By: Andrew Shadura <[email protected]> Description: hostapd - IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator wpagui - graphical user interface for wpa_supplicant wpasupplicant - client support for WPA and WPA2 (IEEE 802.11i) wpasupplicant-udeb - Client support for WPA and WPA2 (IEEE 802.11i) (udeb) Closes: 833507 Changes: wpa (2:2.6-14) unstable; urgency=medium . * Replace the PEM fix patch by Lukasz Siudut with an upstream patch. Thanks to David Benjamin <[email protected]>. * Apply patches from Beniamino Galvani: - Fix race condition in detecting MAC address change - Update MAC address when driver detects a change * Disable WNM to resolve a compatibility issue with wl. Thanks to YOSHINO Yoshihito <[email protected]>. Hopefully really closes: #833507. Checksums-Sha1: dfc3e881141204bca141dbe2247e062f84232eff 2217 wpa_2.6-14.dsc 5fa4bb27ea531d99ce4024713f11138c76cfce82 97632 wpa_2.6-14.debian.tar.xz Checksums-Sha256: 4de54991889b0b95675ec0f1c996e610e8fac7903caddf7f3431e3a2913ad792 2217 wpa_2.6-14.dsc 4aa8a4c61683ed89ac9ac116e27bcea036eea5fb5a8f5483f9f5562e0e1924e9 97632 wpa_2.6-14.debian.tar.xz Files: 0cfc5df20fae3394095ff418d5f03271 2217 net optional wpa_2.6-14.dsc 4eea6e678e16d9edaacca00f1f1ff3d5 97632 net optional wpa_2.6-14.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJaRLdeAAoJEJ1bI/kYT6UUhzQH/Avee8a7PLSJth75g1dVR2xL mFYFir0l7/B5eRBA2Y0rFo2L50yrN+1Y9GDWBuJjlsx03hlP03lmF4trVgMgapcC DiTSIjMafBLeJUrhifjrvKc6ns/YptAGrmzBRLL5ingMwsRwMiKysMIhK8wpKdY9 5HLtCmlSpcXC3qRNOv96usqFfIz4bIjNQ1wO11tnt+ZV4cZ07vNm7dWLUpPIMdkD faFcibisg4O+oCSNsI86DeZwBUUd9ea23Njoc7OYUV4YsPwKuPRMAuWjK34Rb45C Ttv5R8voDcW41b4YcPMVNniNuvUb7y+eRbPGq4ulOQc9wV6BVkRWY9CGMmLDlLc= =XKRf -----END PGP SIGNATURE-----
--- End Message ---
