Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I acquired a JBL Go bluetooth speaker.
It works only in headsetmode on one of my computers (both running stetch, the
other one is running this speaker wih a2dp fine)
I tried different dongles (different chips) and they all don't allow me to use
a2dp, only HSP with this speaker.
I own another bluetooth device and it connects with a2dp fine.
journalctl gives me this:
mai 29 09:42:11 GoonieB gnome-settings-[1856]: Unable to get default sink
mai 29 09:42:11 GoonieB gnome-settings-[1856]: gvc_mixer_card_get_index:
assertion 'GVC_IS_MIXER_CARD (card)' failed
mai 29 09:42:11 GoonieB gnome-settings-[1856]: gvc_mixer_card_get_index:
assertion 'GVC_IS_MIXER_CARD (card)' failed
mai 29 09:42:11 GoonieB gnome-shell[1727]: gvc_mixer_card_get_index: assertion
'GVC_IS_MIXER_CARD (card)' failed
mai 29 09:42:11 GoonieB gnome-shell[1727]: gvc_mixer_card_get_index: assertion
'GVC_IS_MIXER_CARD (card)' failed
AND THEN
kernel: Bluetooth: hci0 SCO packet for unknown connection handle 71
mai 29 09:42:16 GoonieB gnome-control-c[6529]: Device did not have an
appropriate card
mai 29 09:42:16 GoonieB gnome-control-c[6529]: gvc_mixer_card_get_index:
assertion 'GVC_IS_MIXER_CARD (card)' failed
mai 29 09:42:21 GoonieB pulseaudio[2950]: [pulseaudio] module-bluez5-device.c:
Refused to switch profile to a2dp_sink: Not connected
* What exactly did you do (or not do) that was effective (or
ineffective)?
Tried all the fix for such bug shown on the internet
* What was the outcome of this action?
unsuccessful
Hello, Here I attached logs regarding an attempt(s) to use A2dp. there are also pulseaudio log attached as I am investigating it too. I switched harddrives from machines, it worked for a bit then refused to switch to a2dp again :/ Continuing to investigate, Grégory Bahde Doctorant en Géographie UJM / ENSSIB Financé par la Région RA dans le cadre de l'ARC 5 Enseignant UE5 Edition Numérique @ ENSSIB 0619157341----- Mail original ----- De: "gregory bahde" <gregory.bahde@laposte.net> À: "Debian Bug Tracking System" <submit@bugs.debian.org> Envoyé: Lundi 29 Mai 2017 09:46:51 Objet: Bug#863603: bluez: a2dp not working Package: bluez Version: 5.43-2 Severity: normal Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I acquired a JBL Go bluetooth speaker. It works only in headsetmode on one of my computers (both running stetch, the other one is running this speaker wih a2dp fine) I tried different dongles (different chips) and they all don't allow me to use a2dp, only HSP with this speaker. I own another bluetooth device and it connects with a2dp fine. journalctl gives me this: mai 29 09:42:11 GoonieB gnome-settings-[1856]: Unable to get default sink mai 29 09:42:11 GoonieB gnome-settings-[1856]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:11 GoonieB gnome-settings-[1856]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:11 GoonieB gnome-shell[1727]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:11 GoonieB gnome-shell[1727]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed AND THEN kernel: Bluetooth: hci0 SCO packet for unknown connection handle 71 mai 29 09:42:16 GoonieB gnome-control-c[6529]: Device did not have an appropriate card mai 29 09:42:16 GoonieB gnome-control-c[6529]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:21 GoonieB pulseaudio[2950]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected * What exactly did you do (or not do) that was effective (or ineffective)? Tried all the fix for such bug shown on the internet * What was the outcome of this action? unsuccessful
Hello, Here I attached logs regarding an attempt(s) to use A2dp. there are also pulseaudio log attached as I am investigating it too. I switched harddrives from machines, it worked for a bit then refused to switch to a2dp again :/ Continuing to investigate, Grégory Bahde Doctorant en Géographie UJM / ENSSIB Financé par la Région RA dans le cadre de l'ARC 5 Enseignant UE5 Edition Numérique @ ENSSIB 0619157341----- Mail original ----- De: "gregory bahde" <gregory.bahde@laposte.net> À: "Debian Bug Tracking System" <submit@bugs.debian.org> Envoyé: Lundi 29 Mai 2017 09:46:51 Objet: Bug#863603: bluez: a2dp not working Package: bluez Version: 5.43-2 Severity: normal Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I acquired a JBL Go bluetooth speaker. It works only in headsetmode on one of my computers (both running stetch, the other one is running this speaker wih a2dp fine) I tried different dongles (different chips) and they all don't allow me to use a2dp, only HSP with this speaker. I own another bluetooth device and it connects with a2dp fine. journalctl gives me this: mai 29 09:42:11 GoonieB gnome-settings-[1856]: Unable to get default sink mai 29 09:42:11 GoonieB gnome-settings-[1856]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:11 GoonieB gnome-settings-[1856]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:11 GoonieB gnome-shell[1727]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:11 GoonieB gnome-shell[1727]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed AND THEN kernel: Bluetooth: hci0 SCO packet for unknown connection handle 71 mai 29 09:42:16 GoonieB gnome-control-c[6529]: Device did not have an appropriate card mai 29 09:42:16 GoonieB gnome-control-c[6529]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:21 GoonieB pulseaudio[2950]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected * What exactly did you do (or not do) that was effective (or ineffective)? Tried all the fix for such bug shown on the internet * What was the outcome of this action? unsuccessful
Finally solved, It is indeed a gdm3 bug, the #805414 seems a good candidate, I modified /usr/bin/start-pulseaudio-x11 attached ( needed only if using gdm3) and modified /etc/pulse/default.pa (same) I also prevented pulseaudio to load under gdm3 according to this: https://wiki.debia n.org/BluetoothUser/a2dp The odd thing is that without all of this my other headphones where connecting a2dp straight. However Grégory Bahde----- Mail original ----- De: "gregory bahde" <gregory.bahde@laposte.net> À: "gregory bahde" <gregory.bahde@laposte.net>, 863603@bugs.debian.org Cc: "Debian Bug Tracking System" <submit@bugs.debian.org> Envoyé: Mardi 30 Mai 2017 16:43:49 Objet: Re: Bug#863603: bluez: a2dp not working Hello, Here I attached logs regarding an attempt(s) to use A2dp. there are also pulseaudio log attached as I am investigating it too. I switched harddrives from machines, it worked for a bit then refused to switch to a2dp again :/ Continuing to investigate, Grégory Bahde Doctorant en Géographie UJM / ENSSIB Financé par la Région RA dans le cadre de l'ARC 5 Enseignant UE5 Edition Numérique @ ENSSIB 0619157341----- Mail original ----- De: "gregory bahde" <gregory.bahde@laposte.net> À: "Debian Bug Tracking System" <submit@bugs.debian.org> Envoyé: Lundi 29 Mai 2017 09:46:51 Objet: Bug#863603: bluez: a2dp not working Package: bluez Version: 5.43-2 Severity: normal Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I acquired a JBL Go bluetooth speaker. It works only in headsetmode on one of my computers (both running stetch, the other one is running this speaker wih a2dp fine) I tried different dongles (different chips) and they all don't allow me to use a2dp, only HSP with this speaker. I own another bluetooth device and it connects with a2dp fine. journalctl gives me this: mai 29 09:42:11 GoonieB gnome-settings-[1856]: Unable to get default sink mai 29 09:42:11 GoonieB gnome-settings-[1856]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:11 GoonieB gnome-settings-[1856]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:11 GoonieB gnome-shell[1727]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:11 GoonieB gnome-shell[1727]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed AND THEN kernel: Bluetooth: hci0 SCO packet for unknown connection handle 71 mai 29 09:42:16 GoonieB gnome-control-c[6529]: Device did not have an appropriate card mai 29 09:42:16 GoonieB gnome-control-c[6529]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:21 GoonieB pulseaudio[2950]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected * What exactly did you do (or not do) that was effective (or ineffective)? Tried all the fix for such bug shown on the internet * What was the outcome of this action? unsuccessful
Finally solved, It is indeed a gdm3 bug, the #805414 seems a good candidate, I modified /usr/bin/start-pulseaudio-x11 attached ( needed only if using gdm3) and modified /etc/pulse/default.pa (same) I also prevented pulseaudio to load under gdm3 according to this: https://wiki.debia n.org/BluetoothUser/a2dp The odd thing is that without all of this my other headphones where connecting a2dp straight. However Grégory Bahde----- Mail original ----- De: "gregory bahde" <gregory.bahde@laposte.net> À: "gregory bahde" <gregory.bahde@laposte.net>, 863603@bugs.debian.org Cc: "Debian Bug Tracking System" <submit@bugs.debian.org> Envoyé: Mardi 30 Mai 2017 16:43:49 Objet: Re: Bug#863603: bluez: a2dp not working Hello, Here I attached logs regarding an attempt(s) to use A2dp. there are also pulseaudio log attached as I am investigating it too. I switched harddrives from machines, it worked for a bit then refused to switch to a2dp again :/ Continuing to investigate, Grégory Bahde Doctorant en Géographie UJM / ENSSIB Financé par la Région RA dans le cadre de l'ARC 5 Enseignant UE5 Edition Numérique @ ENSSIB 0619157341----- Mail original ----- De: "gregory bahde" <gregory.bahde@laposte.net> À: "Debian Bug Tracking System" <submit@bugs.debian.org> Envoyé: Lundi 29 Mai 2017 09:46:51 Objet: Bug#863603: bluez: a2dp not working Package: bluez Version: 5.43-2 Severity: normal Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I acquired a JBL Go bluetooth speaker. It works only in headsetmode on one of my computers (both running stetch, the other one is running this speaker wih a2dp fine) I tried different dongles (different chips) and they all don't allow me to use a2dp, only HSP with this speaker. I own another bluetooth device and it connects with a2dp fine. journalctl gives me this: mai 29 09:42:11 GoonieB gnome-settings-[1856]: Unable to get default sink mai 29 09:42:11 GoonieB gnome-settings-[1856]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:11 GoonieB gnome-settings-[1856]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:11 GoonieB gnome-shell[1727]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:11 GoonieB gnome-shell[1727]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed AND THEN kernel: Bluetooth: hci0 SCO packet for unknown connection handle 71 mai 29 09:42:16 GoonieB gnome-control-c[6529]: Device did not have an appropriate card mai 29 09:42:16 GoonieB gnome-control-c[6529]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed mai 29 09:42:21 GoonieB pulseaudio[2950]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected * What exactly did you do (or not do) that was effective (or ineffective)? Tried all the fix for such bug shown on the internet * What was the outcome of this action? unsuccessful
Dear Maintainer, After an update in testing a few weeks ago (I'm sorry, I can't remember exaclty the date) A2DP stopped working completely on my system. All my bluetooth speakers/headsets connect properly, but a2dp audio profiles are not available (for example, blueman's "audio profile" context menu doesn't even show submenu). I tried both workarounds described in [1] for the previously mentioned #805414, but none of them worked. Also, this worked fine up until a couple of weeks ago. The only way I am able to send audio to the speakers is if I explicitly set the profile with aplay (`aplay -D bluealsa:PROFILE=a2dp /usr/share/sounds/alsa/Front_Left.wav`), which switches the audio output to the speakers after some time. This does not work for speaker-tests, though (`speaker-test -D bluealsa:PROFILE=a2dp`). If you need any more information, please let me know and I will post it. Thank you very much. Best regards, Flávio Amieiro [1]: https://wiki.debian.org/BluetoothUser/a2dp#Refused_to_switch_profile_to_a2dp_sink:_Not_connected