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

[Brian Murray]

Hello William, or anyone else affected,

Accepted pi-bluetooth into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/pi-
bluetooth/0.1.15ubuntu0~20.04.1 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Changed in: pi-bluetooth (Ubuntu Focal)
       Status: New => Fix Committed

-- 
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
Status in pi-bluetooth source package in Focal:
  Fix Committed

Bug description:
  [Impact]

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

  [Test Case]

   * Boot the Ubuntu Server for Pi 20.04 image on a Raspberry Pi 400.
   * "bluetoothctl"
   * "list" and verify there is no available bluetooth controller
   * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed)
   * "sudo apt install pi-bluetooth"
   * "sudo reboot" (required as bluetooth initialization only occurs during 
      udev activation)
   * "bluetoothctl"
   * "list" and verify there is a single available bluetooth controller
   * "scan on" and bring another discoverable bluetooth device in range; 
      verify it is reported under bluetoothctl
   * Repeat the above steps for the 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