Your message dated Sat, 09 Apr 2022 07:48:47 +0000
with message-id <e1nd5pv-000btp...@fasolo.debian.org>
and subject line Bug#1003907: fixed in wpa 2:2.10-8
has caused the Debian Bug report #1003907,
regarding fails to successfully associate
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 ow...@bugs.debian.org
immediately.)
--
1003907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wpasupplicant
Version: 2:2.10-1
Severity: grave
Hi,
during todays upgrade of wpasupplicant 2:2.9.0-23 to 2:2.10-1 my network
connection was killed (I'm using NetworkManager 1.34.0) and I wasn't
able to successfully connect again, even after a reboot.
Only a downgrade to 2:2.9.0-23 helped.
Attached is the journal log for wpasupplicant.service and a dmesg
output.
Marking as RC so the package doesn't migrate until this has been
investigated.
Regards,
Michael
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages wpasupplicant depends on:
ii adduser 3.118
ii libc6 2.33-2
ii libdbus-1-3 1.12.20-3
ii libnl-3-200 3.4.0-1+b1
ii libnl-genl-3-200 3.4.0-1+b1
ii libnl-route-3-200 3.4.0-1+b1
ii libpcsclite1 1.9.5-1
ii libreadline8 8.1.2-1
ii libssl1.1 1.1.1m-1
ii lsb-base 11.1.0
wpasupplicant recommends no packages.
Versions of packages wpasupplicant suggests:
pn libengine-pkcs11-openssl <none>
pn wpagui <none>
-- Configuration Files:
/etc/wpa_supplicant/ifupdown.sh changed [not included]
-- no debconf information
dmesg
Description: application/json
Jan 18 00:17:02 pluto systemd[1]: Starting WPA supplicant...
Jan 18 00:17:03 pluto systemd[1]: Started WPA supplicant.
Jan 18 00:17:03 pluto wpa_supplicant[664]: Successfully initialized
wpa_supplicant
Jan 18 00:17:04 pluto wpa_supplicant[664]: dbus: fill_dict_with_properties
dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice
dbus_property=P2PDeviceConfig getter failed
Jan 18 00:17:07 pluto wpa_supplicant[664]: wlp3s0: WPS-CANCEL
Jan 18 00:17:07 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate
with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate
with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-ADDED
38:10:d5:8f:38:e2 0
Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with
38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: CTRL-EVENT-ASSOC-REJECT
bssid=38:10:d5:8f:38:e2 status_code=40
Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: SME: Deauth request to the
driver failed
Jan 18 00:17:08 pluto wpa_supplicant[664]: BSSID 38:10:d5:8f:38:e2 ignore list
count incremented to 2, ignoring for 10 seconds
Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate
with 38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz)
Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate
with 38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz)
Jan 18 00:17:09 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-ADDED
38:10:d5:8f:38:e1 0
Jan 18 00:17:09 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with
38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz)
Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate
with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with
38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: CTRL-EVENT-ASSOC-REJECT
bssid=38:10:d5:8f:38:e2 status_code=40
Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-REMOVED
38:10:d5:8f:38:e2 0
Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-REMOVED
38:10:d5:8f:38:e1 0
Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate
with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:13 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate
with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:13 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-ADDED
38:10:d5:8f:38:e2 0
Jan 18 00:17:13 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with
38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:13 pluto wpa_supplicant[664]: wlp3s0: CTRL-EVENT-ASSOC-REJECT
bssid=38:10:d5:8f:38:e2 status_code=40
Jan 18 00:17:13 pluto wpa_supplicant[664]: wlp3s0: SME: Deauth request to the
driver failed
Jan 18 00:17:13 pluto wpa_supplicant[664]: BSSID 38:10:d5:8f:38:e2 ignore list
count incremented to 2, ignoring for 10 seconds
Jan 18 00:17:14 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate
with 38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz)
Jan 18 00:17:16 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate
with 38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz)
Jan 18 00:17:16 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-ADDED
38:10:d5:8f:38:e1 0
Jan 18 00:17:16 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with
38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz)
Jan 18 00:17:16 pluto wpa_supplicant[664]: wlp3s0: CTRL-EVENT-ASSOC-REJECT
bssid=38:10:d5:8f:38:e1 status_code=40
Jan 18 00:17:16 pluto wpa_supplicant[664]: wlp3s0: SME: Deauth request to the
driver failed
Jan 18 00:17:16 pluto wpa_supplicant[664]: wlp3s0:
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="myessid" auth_failures=1 duration=10
reason=CONN_FAILED
Jan 18 00:17:26 pluto wpa_supplicant[664]: wlp3s0: CTRL-EVENT-SSID-REENABLED
id=0 ssid="myessid"
Jan 18 00:17:26 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate
with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:26 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with
38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:26 pluto wpa_supplicant[664]: wlp3s0: CTRL-EVENT-ASSOC-REJECT
bssid=38:10:d5:8f:38:e2 status_code=40
Jan 18 00:17:26 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-REMOVED
38:10:d5:8f:38:e2 0
Jan 18 00:17:26 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-REMOVED
38:10:d5:8f:38:e1 0
Jan 18 00:17:26 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate
with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:27 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate
with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:27 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-ADDED
38:10:d5:8f:38:e2 0
Jan 18 00:17:27 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with
38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz)
Jan 18 00:17:27 pluto wpa_supplicant[664]: wlp3s0: CTRL-EVENT-ASSOC-REJECT
bssid=38:10:d5:8f:38:e2 status_code=40
Jan 18 00:17:27 pluto wpa_supplicant[664]: wlp3s0: SME: Deauth request to the
driver failed
Jan 18 00:17:27 pluto wpa_supplicant[664]: BSSID 38:10:d5:8f:38:e2 ignore list
count incremented to 3, ignoring for 60 seconds
Jan 18 00:17:27 pluto wpa_supplicant[664]: wlp3s0:
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="myessid" auth_failures=2 duration=20
reason=CONN_FAILED
--- End Message ---
--- Begin Message ---
Source: wpa
Source-Version: 2:2.10-8
Done: Andrej Shadura <andre...@debian.org>
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 1003...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrej Shadura <andre...@debian.org> (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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 09 Apr 2022 09:28:35 +0200
Source: wpa
Architecture: source
Version: 2:2.10-8
Distribution: unstable
Urgency: medium
Maintainer: Debian wpasupplicant Maintainers <w...@packages.debian.org>
Changed-By: Andrej Shadura <andre...@debian.org>
Closes: 1003907
Changes:
wpa (2:2.10-8) unstable; urgency=medium
.
* Pull the defconfig updates from the upstream’s Git.
* Add an upstream patch: AP: guard FT-SAE code with CONFIG_IEEE80211R_AP.
* Declare Breaks against NM without this patch (Closes: #1003907):
- supplicant: enable WPA3 transition mode only when interface supports PMF
Checksums-Sha1:
5bc3c20c1c15a4041f62ca5c6c6af70fc194414e 2179 wpa_2.10-8.dsc
8071cfe87c01a1ca90d62f26ada677f37039a193 86236 wpa_2.10-8.debian.tar.xz
Checksums-Sha256:
1a46d0affc9adc2c3a9e990ce1c3e8c26fcfee399a9b9a979924ac285a71f1e4 2179
wpa_2.10-8.dsc
7f57a7212b7dd2740803b8bcf5591fb363d98266de567f73a7bf475dd2f4e729 86236
wpa_2.10-8.debian.tar.xz
Files:
fefe0cfd6a27d944f90bb3b947945be3 2179 net optional wpa_2.10-8.dsc
c5efa22816286290806d23f6b448efed 86236 net optional wpa_2.10-8.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCYlE2TwAKCRDoRGtKyMdy
YY1zAP0fCaD167Q3EqM3l8GyMhS77+H4KfgNYauZrlYpXxeVZQEAvkX4R0YtNwKH
rth5CTdxNN+Ly6s+Ft5Ee5AqucI9AA0=
=fjC8
-----END PGP SIGNATURE-----
--- End Message ---
