Activity log for bug #1921915

Date Who What changed Old value New value Message
2021-03-30 14:44:35 Dave Jones bug added bug
2021-03-30 14:44:45 Dave Jones pi-bluetooth (Ubuntu): assignee Dave Jones (waveform)
2021-03-30 14:45:05 Dave Jones nominated for series Ubuntu Focal
2021-03-30 14:45:05 Dave Jones bug task added pi-bluetooth (Ubuntu Focal)
2021-03-30 14:45:05 Dave Jones nominated for series Ubuntu Hirsute
2021-03-30 14:45:05 Dave Jones bug task added pi-bluetooth (Ubuntu Hirsute)
2021-03-30 14:45:05 Dave Jones nominated for series Ubuntu Groovy
2021-03-30 14:45:05 Dave Jones bug task added pi-bluetooth (Ubuntu Groovy)
2021-04-01 15:22:54 Launchpad Janitor pi-bluetooth (Ubuntu Hirsute): status New Fix Released
2021-04-09 19:34:38 William Wilson pi-bluetooth (Ubuntu Groovy): assignee William Wilson (jawn-smith)
2021-04-09 19:34:40 William Wilson pi-bluetooth (Ubuntu Focal): assignee William Wilson (jawn-smith)
2021-04-19 17:33:53 William Wilson pi-bluetooth (Ubuntu Focal): status New In Progress
2021-04-19 17:33:57 William Wilson pi-bluetooth (Ubuntu Groovy): status New In Progress
2021-04-26 16:13:59 William Wilson attachment added Focal SRU https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1921915/+attachment/5492485/+files/lp1921915_focal.debdiff
2021-04-26 16:14:21 William Wilson attachment added Groovy SRU https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1921915/+attachment/5492486/+files/lp1921915_groovy.debdiff
2021-04-27 19:41:47 William Wilson description Under later versions of the Ubuntu kernel (5.8) on the CM4 and (possibly?) some models of the Pi 400, the bluetooth controller is not activated by the pi-bluetooth package. This appears to be due to two issues: * The mmcnr device is mistaken for a bluetooth controller. This in itself is harmless, but results in a spurious hci0 device. The existence of this device causes the btuart script to skip configuring the "real" bluetooth device (as it thinks it is already configured) * The btuart script also attempts a match against the device-tree's model name looking for "Raspberry Pi 4" which doesn't match "Raspberry Pi Compute Module 4". The upstream repository currently has commits for both these fixes but no release has been made yet. It is proposed to backport these patches into an -ubuntu2 version of the package in the meantime. [Impact] Without these patches, Bluetooth is inoperable on the CM4 [Test Case] * Boot the Ubuntu Desktop for Pi image on a CM4. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails [Regression Potential] The main concern would be the backported versions of pi-bluetooth not integrating well with other packages. We are mitigating this concern by also SRUing Bluez and linux-firmware-raspi2 to focal and groovy. [Original Description] Under later versions of the Ubuntu kernel (5.8) on the CM4 and (possibly?) some models of the Pi 400, the bluetooth controller is not activated by the pi-bluetooth package. This appears to be due to two issues: * The mmcnr device is mistaken for a bluetooth controller. This in itself is harmless, but results in a spurious hci0 device. The existence of this device causes the btuart script to skip configuring the "real" bluetooth device (as it thinks it is already configured) * The btuart script also attempts a match against the device-tree's model name looking for "Raspberry Pi 4" which doesn't match "Raspberry Pi Compute Module 4". The upstream repository currently has commits for both these fixes but no release has been made yet. It is proposed to backport these patches into an -ubuntu2 version of the package in the meantime.
2021-04-27 20:34:16 Brian Murray pi-bluetooth (Ubuntu Groovy): status In Progress Fix Committed
2021-04-27 20:34:19 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2021-04-27 20:34:21 Brian Murray bug added subscriber SRU Verification
2021-04-27 20:34:25 Brian Murray tags verification-needed verification-needed-groovy
2021-04-28 14:51:44 Dave Jones description [Impact] Without these patches, Bluetooth is inoperable on the CM4 [Test Case] * Boot the Ubuntu Desktop for Pi image on a CM4. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails [Regression Potential] The main concern would be the backported versions of pi-bluetooth not integrating well with other packages. We are mitigating this concern by also SRUing Bluez and linux-firmware-raspi2 to focal and groovy. [Original Description] Under later versions of the Ubuntu kernel (5.8) on the CM4 and (possibly?) some models of the Pi 400, the bluetooth controller is not activated by the pi-bluetooth package. This appears to be due to two issues: * The mmcnr device is mistaken for a bluetooth controller. This in itself is harmless, but results in a spurious hci0 device. The existence of this device causes the btuart script to skip configuring the "real" bluetooth device (as it thinks it is already configured) * The btuart script also attempts a match against the device-tree's model name looking for "Raspberry Pi 4" which doesn't match "Raspberry Pi Compute Module 4". The upstream repository currently has commits for both these fixes but no release has been made yet. It is proposed to backport these patches into an -ubuntu2 version of the package in the meantime. [Impact] Without these patches, Bluetooth is inoperable on the CM4 [Test Case] * Boot an ubuntu image (server/desktop) on a Pi CM4 * "sudo apt update" * "sudo apt upgrade" * If on server (not desktop) - "sudo apt install pi-bluetooth" - "sudo reboot" * "bluetoothctl" * "list" (show all available controllers) and verify there is no output * 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 [Regression Potential] The main concern would be the backported versions of pi-bluetooth not integrating well with other packages. We are mitigating this concern by also SRUing Bluez and linux-firmware-raspi2 to focal and groovy. [Original Description] Under later versions of the Ubuntu kernel (5.8) on the CM4 and (possibly?) some models of the Pi 400, the bluetooth controller is not activated by the pi-bluetooth package. This appears to be due to two issues: * The mmcnr device is mistaken for a bluetooth controller. This in itself is harmless, but results in a spurious hci0 device. The existence of this device causes the btuart script to skip configuring the "real" bluetooth device (as it thinks it is already configured) * The btuart script also attempts a match against the device-tree's model name looking for "Raspberry Pi 4" which doesn't match "Raspberry Pi Compute Module 4". The upstream repository currently has commits for both these fixes but no release has been made yet. It is proposed to backport these patches into an -ubuntu2 version of the package in the meantime.
2021-05-02 02:01:57 Mathew Hodson pi-bluetooth (Ubuntu): importance Undecided Medium
2021-05-02 02:01:59 Mathew Hodson pi-bluetooth (Ubuntu Focal): importance Undecided Medium
2021-05-02 02:02:01 Mathew Hodson pi-bluetooth (Ubuntu Groovy): importance Undecided Medium
2021-05-02 02:02:03 Mathew Hodson pi-bluetooth (Ubuntu Hirsute): importance Undecided Medium
2021-05-10 22:42:17 William Wilson tags verification-needed verification-needed-groovy verification-done verification-done-groovy
2021-05-10 22:48:20 William Wilson pi-bluetooth (Ubuntu Focal): status In Progress Fix Committed
2021-05-11 15:54:31 Launchpad Janitor pi-bluetooth (Ubuntu Groovy): status Fix Committed Fix Released
2021-05-11 15:54:35 Brian Murray removed subscriber Ubuntu Stable Release Updates Team
2021-05-19 19:24:36 William Wilson pi-bluetooth (Ubuntu Focal): status Fix Committed Fix Released