Sorry about that, here's some more info: The regression from LP #2096979 [1] only appears on Noble and later, so there is no new package version for Jammy and lower.
[Tested versions (0ubuntu1)] trusty 2024.10.07-0ubuntu1~14.04.1 xenial 2024.10.07-0ubuntu1~16.04.1 bionic 2024.10.07-0ubuntu1~18.04.1 Installed package without errors on a VM. The regulatory.bin file is present. focal 2024.10.07-0ubuntu1~20.04.1 jammy 2024.10.07-0ubuntu1~22.04.1 Installed package without errors on a baremetal device running the release. iw reg get/set works. [Tested versions (0ubuntu2)] noble 2024.10.07-0ubuntu2~24.04.1 oracular 2024.10.07-0ubuntu2~24.10.1 plucky 2024.10.07-0ubuntu2 Installed package without errors on a baremetal device running the classic release. iw reg get/set works. Installed package without errors on an FDE VM, and firmware files are correctly diverted away from /lib/firmware. -- [1] https://bugs.launchpad.net/bugs/2096979 ** Tags removed: verification-needed-jammy verification-needed-noble verification-needed-oracular ** Tags added: verification-done-jammy verification-done-noble verification-done-oracular -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/2094190 Title: 2024.10.07 new upstream release Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Trusty: New Status in wireless-regdb source package in Xenial: New Status in wireless-regdb source package in Bionic: New Status in wireless-regdb source package in Focal: New Status in wireless-regdb source package in Jammy: Fix Committed Status in wireless-regdb source package in Noble: Fix Committed Status in wireless-regdb source package in Oracular: Fix Committed Status in wireless-regdb source package in Plucky: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda (<< k4.15) or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/2094190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
