| 2021-04-27 23:34:39 |
William Wilson |
bug |
|
|
added bug |
| 2021-04-27 23:38:59 |
William Wilson |
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.
* Run `bluetoothctl devices`
* 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. |
[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. |
|
| 2021-04-27 23:47:27 |
William Wilson |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2021-04-27 23:51:12 |
William Wilson |
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. |
[Impact]
* Without the pi-bluetooth changes in hirsute, bluetooth will not work on the Pi 4, 400 or CM4.
[Test Case]
* Boot the Ubuntu Server for Pi image on a Raspberry Pi 4.
* Verify the command `bluetoothctl devices` fails with the
error "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. |
|
| 2021-04-27 23:52:57 |
William Wilson |
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 Server for Pi image on a Raspberry Pi 4.
* Verify the command `bluetoothctl devices` fails with the
error "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. |
[Impact]
* Without the pi-bluetooth changes in hirsute, bluetooth will not work on the Pi 4, 400 or CM4.
[Test Case]
* Boot the Ubuntu Server for Pi 20.04 image on a Raspberry Pi 4.
* Verify the command `bluetoothctl devices` fails with the
error "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. |
|
| 2021-04-28 00:01:52 |
William Wilson |
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 Server for Pi 20.04 image on a Raspberry Pi 4.
* Verify the command `bluetoothctl devices` fails with the
error "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. |
[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.
* Verify the command `bluetoothctl devices` fails with the
error "No default controller available"
* 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. |
|
| 2021-04-28 00:02:24 |
William Wilson |
attachment added |
|
lp1921915_focal.debdiff https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+attachment/5492937/+files/lp1921915_focal.debdiff |
|
| 2021-04-28 14:56:53 |
William Wilson |
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.
* Verify the command `bluetoothctl devices` fails with the
error "No default controller available"
* 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. |
[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. |
|
| 2021-05-02 01:59:43 |
Mathew Hodson |
nominated for series |
|
Ubuntu Focal |
|
| 2021-05-02 01:59:43 |
Mathew Hodson |
bug task added |
|
pi-bluetooth (Ubuntu Focal) |
|
| 2021-05-02 02:01:16 |
Mathew Hodson |
pi-bluetooth (Ubuntu): importance |
Undecided |
Medium |
|
| 2021-05-02 02:01:18 |
Mathew Hodson |
pi-bluetooth (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2021-05-02 02:02:38 |
Mathew Hodson |
tags |
|
upgrade-software-version |
|
| 2021-05-07 16:45:05 |
William Wilson |
tags |
upgrade-software-version |
upgrade-software-version verification-needed verification-needed-focal |
|
| 2021-05-07 20:43:57 |
Brian Murray |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2021-05-07 20:50:52 |
Brian Murray |
pi-bluetooth (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2021-05-07 20:50:54 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-05-07 20:50:57 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2021-05-07 21:12:45 |
William Wilson |
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. |
[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. |
|
| 2021-05-10 21:11:17 |
William Wilson |
tags |
upgrade-software-version verification-needed verification-needed-focal |
upgrade-software-version verification-done verification-done-focal |
|
| 2021-05-10 21:11:28 |
William Wilson |
pi-bluetooth (Ubuntu): assignee |
|
William Wilson (jawn-smith) |
|
| 2021-05-10 21:11:30 |
William Wilson |
pi-bluetooth (Ubuntu Focal): assignee |
|
William Wilson (jawn-smith) |
|
| 2021-05-19 16:57:23 |
Brian Murray |
pi-bluetooth (Ubuntu): status |
New |
Invalid |
|
| 2021-05-19 16:57:51 |
Launchpad Janitor |
pi-bluetooth (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-05-19 16:57:55 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
