bluetooth: Google Nest not working

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1956147/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

This is not my system, so I cannot debug a lot.

Linux kernel 5.4.x is used, and Linux logs hci related messages, and bluetoothd also segfaults. (Ubuntu noticed the crash, and should have uploaded the resulting dumps.)

What fixed it was using `a2dp.py`:

```
$ curl "https://gist.githubusercontent.com/pylover/d68be364adac5f946887b85e6ed6e7ae/raw/install.sh" | sh
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
100 314 100 314 0 0 664 0 --:--:-- --:--:-- --:--:-- 670
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
100 11977 100 11977 0 0 27402 0 --:--:-- --:--:-- --:--:-- 27470
a2dp installation was successfull.
Run a2dp.py [-h/--help] and enjoy the HiFi music!
$ a2dp.py
Connection MADE
Selecting device:
1. XXX
2. XXX
3. 14:C1:4E:99:XX:XX Office speaker
4. XXX
5. XXX
Select device[1]:
3
Device MAC: 14:C1:4E:99:XX:XX
Device ID: bluez_card.14_C1_4E_99_XX_XX
Sink: bluez_sink.14_C1_4E_99_XX_XX
Updating default sink to bluez_sink.14_C1_4E_99_XX_XX
Setting the off profile
Disconnecting the device.
Connecting again.
Device ID: bluez_card.14_C1_4E_99_XX_XX
Setting the a2dp profile
Updating default sink to bluez_sink.14_C1_4E_99_XX_XX
Ignoring: Command: pacmd list-sink-inputs | grep "index:" failed with status: 1
stderr:
Exiting bluetoothctl
"Enjoy" the HiFi stereo music
```

Comparing Ubuntu 20.04 to Debian Unstable probably isn't fair because the former is a couple of years older. Please try either Ubuntu 21.10:

  https://ubuntu.com/download/desktop

or the preview of Ubuntu 22.04:

  http://cdimage.ubuntu.com/daily-live/current/

I understand, that bugs are probably fixed in newer versions.

https://ubuntu.com/#download still offers Ubuntu 20.04 for desktops, and even highlighted green. So what functionality can users expect?

Anyway, I just wanted to report it, and, as it is not my device, I am also unable to debug more.

Generally Ubuntu 20.04 is more recommended because it is LTS (long term supported). I was only suggesting 21.10 or 22.04 because those would be more in line with what you see in Debian Unstable. Although I just tried 22.04 and find it's still not as up to date as Debian compared to the screenshot in comment #1. That will change in the next couple of months.

I'm still not sure if gnome-bluetooth is the correct component here. Ubuntu 22.04 already has gnome-bluetooth 3.34.5-4 which is the latest.

We also have the latest BlueZ in Ubuntu already.

Maybe PulseAudio needs to be added here because that is where Bluetooth audio is implemented.

Yes, thank you for assigning the right component.

Personally, for desktops, I would always recommend the latest release. I think a lot of users do not know the difference, and just click the green button.

> We also have the latest BlueZ in Ubuntu already.

Do you mean 21.10, which has 5.60-0ubuntu2.1? Ubuntu 20.04 has 5.53-0ubuntu3.4.

Also, as written, `bluetoothd` seemed to have crashed several times, and the user allowed the crash reporter to upload the traces. Where can those be found?

I mean in Ubuntu 22.04, BlueZ is version 5.62.

To find historical crashes from a machine you can try these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

The system was updated from Ubuntu 20.04 to 21.10, but it’s still not working out of the box without the script `a2dp.py`.

I am not able to work more on the issue, as I do not have the environment, but maybe Canonical and Google should work more closely together on the QA side.