[Bug 1926378] [NEW] SRU pi-bluetooth from hirsute to focal to enable all models

[William Wilson]

Public bug reported:

[Impact]

 * Without the pi-bluetooth changes in hirsute, bluetooth will not work
on the Pi 4, 400 or CM4.

[Test Case]

 * Boot the Ubuntu Desktop for Pi image on a Raspberry Pi 4.
 * Start the Settings application and switch to the Bluetooth tab
 * Verify that Bluetooth is not enabled and attempting to activate
   it fails
 * Boot the Ubuntu Server for Pi image on a Raspberry Pi 4.
 * Verify `bluetoothctl devices` fails with the error message "No default
   controller available
 * Repeat the above steps for the Pi 400 and CM4

[Regression Potential]

There are multiple changes being SRU'd, but since the linux-firmware-
raspi2 and bluez packages are also being SRUd, the risk of regression
should be fairly low. These changes have worked well in hirsute for some
time.

** Affects: pi-bluetooth (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  [Impact]
  
-  * Without the pi-bluetooth changes in hirsute, bluetooth will not work
+  * Without the pi-bluetooth changes in hirsute, bluetooth will not work
  on the Pi 4, 400 or CM4.
  
  [Test Case]
  
-  * Boot the Ubuntu Desktop for Pi image on a Raspberry Pi 4.
-  * Start the Settings application and switch to the Bluetooth tab
-  * Verify that Bluetooth is not enabled and attempting to activate it fails
-  * Boot the Ubuntu Server for Pi image on a Raspberry Pi 4.
-  * Run `bluetoothctl devices`
-  * Repeat the above steps for the Pi 400 and CM4
+  * Boot the Ubuntu Desktop for Pi image on a Raspberry Pi 4.
+  * Start the Settings application and switch to the Bluetooth tab
+  * Verify that Bluetooth is not enabled and attempting to activate
+    it fails
+  * Boot the Ubuntu Server for Pi image on a Raspberry Pi 4.
+  * Verify `bluetoothctl devices` fails with the error message "No default
+    controller available
+  * Repeat the above steps for the Pi 400 and CM4
  
  [Regression Potential]
  
  There are multiple changes being SRU'd, but since the linux-firmware-
  raspi2 and bluez packages are also being SRUd, the risk of regression
  should be fairly low. These changes have worked well in hirsute for some
  time.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pi-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1926378

Title:
  SRU pi-bluetooth from hirsute to focal to enable all models

Status in pi-bluetooth package in Ubuntu:
  New

Bug description:
  [Impact]

   * Without the pi-bluetooth changes in hirsute, bluetooth will not
  work on the Pi 4, 400 or CM4.

  [Test Case]

   * Boot the Ubuntu Desktop for Pi image on a Raspberry Pi 4.
   * Start the Settings application and switch to the Bluetooth tab
   * Verify that Bluetooth is not enabled and attempting to activate
     it fails
   * Boot the Ubuntu Server for Pi image on a Raspberry Pi 4.
   * Verify `bluetoothctl devices` fails with the error message "No default
     controller available
   * Repeat the above steps for the Pi 400 and CM4

  [Regression Potential]

  There are multiple changes being SRU'd, but since the linux-firmware-
  raspi2 and bluez packages are also being SRUd, the risk of regression
  should be fairly low. These changes have worked well in hirsute for
  some time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+subscriptions