This bug was fixed in the package network-manager - 1.46.0-1ubuntu2.2
---------------
network-manager (1.46.0-1ubuntu2.2) noble; urgency=medium
* d/control: Avoid calling into half-upgraded Netplan (LP: #2033259)
NM calls 'netplan generate', which will crash if new libnetplan1 is already
installed, but we're calling the old netplan.io Python code expecting the
old libnetplan0 API.
network-manager (1.46.0-1ubuntu2.1) noble; urgency=medium
* d/p/wifi-fix-the-ranges-of-5-GHz-and-6-GHz-bands.patch
d/p/wifi-fix-enumeration-of-6-GHz-channels-from-wiphy.patch
- Fix detection of 6 GHz band capability for WiFi devices (LP: #2084731)
-- Lukas Märdian <sl...@ubuntu.com> Wed, 23 Oct 2024 13:04:42 +0200
** Changed in: network-manager (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2084731
Title:
Not report 6 GHz capability correctly
Status in OEM Priority Project:
New
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Noble:
Fix Released
Bug description:
[Impact]
network-manager not report 6GHz capability even hardware able to
support 6GHz band
[Test Plan]
1. nmcli -f wifi-properties.6ghz device show $DEV
2. should get correct result on 6GHz band enabled system
"WIFI-PROPERTIES.6GHZ: yes"
[Where problems could occur]
If the parsing is incorrect, the status of WIFI-PROPERTIES.2GHZ,
WIFI-PROPERTIES.5GHZ and WIFI-PROPERTIES.6GHZ may be incorrect.
A codesearch query suggests those properties are only used by settings
panels to reflect capabilities in the UI so if something went wrong
the visible impact should be to have wrong information displayed.
This SRU add attribute NL80211_ATTR_SPLIT_WIPHY_DUMP to split wiphy
data across multiple messages, then parse the message one by one to
get full supported frequencies. This attribute added after Linux 3.9.
And there is not other function impact. The risk should be low
[Other information]
upstream merge proposal
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1899
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2084731/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
