2022.08.12 new upstream release
Bug #2004171 reported by
Dimitri John Ledkov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| wireless-regdb (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| Trusty |
New
|
Undecided
|
Unassigned | ||
| Xenial |
New
|
Undecided
|
Unassigned | ||
| Bionic |
New
|
Undecided
|
Unassigned | ||
| Focal |
New
|
Undecided
|
Unassigned | ||
| Jammy |
New
|
Undecided
|
Unassigned | ||
| Kinetic |
Won't Fix
|
Undecided
|
Unassigned | ||
| Lunar |
New
|
Undecided
|
Unassigned | ||
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 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.
| information type: | Public → Public Security |
Revision history for this message
| Utkarsh Gupta (utkarsh) wrote | #1 |
| Changed in wireless-regdb (Ubuntu Kinetic): | |
| status: | New → Won't Fix |
To post a comment you must log in.
Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release.