Public bug reported:

[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.

** Affects: wireless-regdb (Ubuntu)
     Importance: Undecided
     Assignee: Seth Forshee (sforshee)
         Status: In Progress

** Affects: wireless-regdb (Ubuntu Bionic)
     Importance: Undecided
     Assignee: Seth Forshee (sforshee)
         Status: Confirmed

** Affects: wireless-regdb (Ubuntu Focal)
     Importance: Undecided
     Assignee: Seth Forshee (sforshee)
         Status: Confirmed

** Affects: wireless-regdb (Ubuntu Hirsute)
     Importance: Undecided
     Assignee: Seth Forshee (sforshee)
         Status: Confirmed

** Affects: wireless-regdb (Ubuntu Impish)
     Importance: Undecided
     Assignee: Seth Forshee (sforshee)
         Status: In Progress

** Also affects: wireless-regdb (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: wireless-regdb (Ubuntu Impish)
   Importance: Undecided
     Assignee: Seth Forshee (sforshee)
       Status: In Progress

** Also affects: wireless-regdb (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: wireless-regdb (Ubuntu Hirsute)
   Importance: Undecided
       Status: New

** Changed in: wireless-regdb (Ubuntu Bionic)
       Status: New => Confirmed

** Changed in: wireless-regdb (Ubuntu Bionic)
     Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: wireless-regdb (Ubuntu Focal)
       Status: New => Confirmed

** Changed in: wireless-regdb (Ubuntu Focal)
     Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: wireless-regdb (Ubuntu Hirsute)
       Status: New => Confirmed

** Changed in: wireless-regdb (Ubuntu Hirsute)
     Assignee: (unassigned) => Seth Forshee (sforshee)

-- 
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/1941955

Title:
  New upstream release 2021.08.28

Status in wireless-regdb package in Ubuntu:
  In Progress
Status in wireless-regdb source package in Bionic:
  Confirmed
Status in wireless-regdb source package in Focal:
  Confirmed
Status in wireless-regdb source package in Hirsute:
  Confirmed
Status in wireless-regdb source package in Impish:
  In Progress

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+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

Reply via email to