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:
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.
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 0000-1000- 8000-00805f9b34 fb) 0000-1000- 8000-00805f9b34 fb) 0000-1000- 8000-00805f9b34 fb) 0000-1000- 8000-00805f9b34 fb) 0000-1000- 8000-00805f9b34 fb) 0000-1000- 8000-00805f9b34 fb
Name: 8XXPlantronics
Alias: 8XXPlantronics
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset (00001108-
UUID: Audio Sink (0000110b-
UUID: A/V Remote Control Target (0000110c-
UUID: Advanced Audio Distribu.. (0000110d-
UUID: A/V Remote Control (0000110e-
UUID: Handsfree (0000111e-
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.