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

[William Wilson]

[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. In the past, other updates to this package have caused regressions on other Pi models such as the 2, 3, and 4. Though unlikely, that could potentially occur with this change as well.

[Brian Murray (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.

[William Wilson (jawn-smith)]

The verification passed for focal.

********* On Pi 400 **********
ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2
bluez:
  Installed: 5.53-0ubuntu3
  Candidate: 5.53-0ubuntu3.1
  Version table:
     5.53-0ubuntu3.1 500
        500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages
 *** 5.53-0ubuntu3 500
        500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages
        100 /var/lib/dpkg/status
pi-bluetooth:
  Installed: 0.1.10ubuntu6
  Candidate: 0.1.15ubuntu0~20.04.1
  Version table:
     0.1.15ubuntu0~20.04.1 500
        500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages
 *** 0.1.10ubuntu6 500
        500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages
        100 /var/lib/dpkg/status
linux-firmware-raspi2:
  Installed: 3-0ubuntu2~20.04.1
  Candidate: 4-0ubuntu0~20.04.1
  Version table:
     4-0ubuntu0~20.04.1 500
        500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages
 *** 3-0ubuntu2~20.04.1 500
        500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 Packages
        100 /var/lib/dpkg/status
     1.20200212-0ubuntu1 500
        500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages
ubuntu@ubuntu:~$ bluetoothctl devices
No default controller available

ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2
bluez:
  Installed: 5.53-0ubuntu3.1
  Candidate: 5.53-0ubuntu3.1
  Version table:
 *** 5.53-0ubuntu3.1 500
        500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages
        100 /var/lib/dpkg/status
     5.53-0ubuntu3 500
        500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages
pi-bluetooth:
  Installed: 0.1.15ubuntu0~20.04.1
  Candidate: 0.1.15ubuntu0~20.04.1
  Version table:
 *** 0.1.15ubuntu0~20.04.1 500
        500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages
        100 /var/lib/dpkg/status
     0.1.10ubuntu6 500
        500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages
linux-firmware-raspi2:
  Installed: 4-0ubuntu0~20.04.1
  Candidate: 4-0ubuntu0~20.04.1
  Version table:
 *** 4-0ubuntu0~20.04.1 500
        500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages
        100 /var/lib/dpkg/status
     3-0ubuntu2~20.04.1 500
        500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 Packages
     1.20200212-0ubuntu1 500
        500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages
ubuntu@ubuntu:~$ bluetoothctl
Agent registered
[CHG] Controller DC:A6:32:F6:84:4E Pairable: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller DC:A6:32:F6:84:4E Discovering: yes
[NEW] Device 28:11:A5:D5:AC:98 28-11-A5-D5-AC-98
[NEW] Device 68:27:37:05:F4:ED [TV] Samsung 6 Series (55)
[NEW] Device 5B:1B:6F:46:F3:00 5B-1B-6F-46-F3-00
[NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M
[NEW] Device 42:25:C8:1B:5F:D2 42-25-C8-1B-5F-D2
[NEW] Device 64:FF:0A:21:B1:70 64-FF-0A-21-B1-70
[CHG] Device 28:11:A5:D5:AC:98 RSSI: -62
[CHG] Device 28:11:A5:D5:AC:98 TxPower: 8
[CHG] Device 28:11:A5:D5:AC...

[Chris Halse Rogers (raof)]

This is apparently fixed in Hirsute, and now the Focal SRU, but that would seem to leave Groovy without working bluetooth on the Pi 400 and CM4? Is there any plan for an SRU to Groovy, too?

[Brian Murray (brian-murray)]

This was actually fixed in groovy but tracked in a different SRU bug.

pi-bluetooth (0.1.15ubuntu1.1~20.10.1) groovy; urgency=medium

  * Merged upstream fixes for CM4 and Pi 400 (LP: #1921915)

 -- William 'jawn-smith' Wilson <email address hidden> Mon, 26 Apr 2021 09:40:19 -0500

[Launchpad Janitor (janitor)]

This bug was fixed in the package pi-bluetooth - 0.1.15ubuntu0~20.04.1

---------------
pi-bluetooth (0.1.15ubuntu0~20.04.1) focal; urgency=medium

  * SRU pi-bluetooth from hirsute to focal. This fixes bluetooth issues on
    the Raspberry Pi 4, 400, and CM4. (LP: #1926378)

 -- William 'jawn-smith' Wilson <email address hidden> Tue, 27 Apr 2021 18:27:36 -0500

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for pi-bluetooth has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.