Ok, false alarm. It wasn't showing up because it doesn't seem to
reconnect automatically if I leave the headset on during a relog/reboot.
After using bluetoothctl to reconnect the headset, pulse seems to work
perfectly every time, so I am unable to reproduce the problem.
Given the original reporter's bluetoothctl info, I notice only one
difference between my headset and the one in the report, and that is an
unknown UUID. Here is mine for reference:
Device 00:19:7F:69:B0:7D
Name: 8XXPlantronics
Alias: 8XXPlantronics
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb
If people who are experiencing this problem could use a working
pulseaudio to obtain info about their bluetooth devices via the pacmd
list-cards command, that would be useful.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574324
Title:
pulseaudio crashes when connecting to bluetooth headphones (due to
ubuntu changes?)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
