Hello Dirk, or anyone else affected,

Accepted network-manager into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.46.0-1ubuntu2.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-noble

-- 
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 Committed

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

Reply via email to