Bug 1830397
| Summary: | bluetooth unable to connect to bluetooth headphones | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Adam Miller <admiller> |
| Component: | bluez | Assignee: | gopal krishna tiwari <gtiwari> |
| Status: | CLOSED ERRATA | QA Contact: | Ken Benoit <kbenoit> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.2 | CC: | darcari, hwkernel-mgr, ikke, jwboyer, jwesterd, kbenoit, mhaicman, oliver, rvr, sbarcomb |
| Target Milestone: | rc | Keywords: | Reopened |
| Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | bluez-5.52-1.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-04 02:03:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Adam Miller
2020-05-01 20:04:55 UTC
Hey Adam, I just tried to reproduce this on my T480s running 8.2 and bluez-5.50-3 and I cannot reproduce this with a pair of Microsoft surface headphones. Can you provide the following information: 1) Did this ever work for you in RHEL8? 2) What type of headset is failing? 3) Do you have the ability to test a second type of headset? 4) Can you attach an sosreport from the system having the issue? -Steve (In reply to Steve Barcomb from comment #1) > Hey Adam, > I just tried to reproduce this on my T480s running 8.2 and bluez-5.50-3 and > I cannot reproduce this with a pair of Microsoft surface headphones. Can > you provide the following information: > > 1) Did this ever work for you in RHEL8? > > 2) What type of headset is failing? > > 3) Do you have the ability to test a second type of headset? > > 4) Can you attach an sosreport from the system having the issue? > > -Steve Along with what Steve has mentioned can you please check the pulseaudio package installed for bluetooth ? Following is the link to download the pulseaudio package for RHEL https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=12292 Gopal (In reply to Steve Barcomb from comment #1) > Hey Adam, > I just tried to reproduce this on my T480s running 8.2 and bluez-5.50-3 and > I cannot reproduce this with a pair of Microsoft surface headphones. Can > you provide the following information: > > 1) Did this ever work for you in RHEL8? > No, never. Works fine in Fedora 30, 31, and 32 though. > 2) What type of headset is failing? Anker SoundBuds Slim+ Anker PowerConf Bluetooth Speaker phone. > > 3) Do you have the ability to test a second type of headset? > I'll have to buy some, but yes. > 4) Can you attach an sosreport from the system having the issue? Attached > > -Steve I have similar errors with some Jabra Active 75t and Bose QC35 headphones as well. (In reply to Josh Boyer from comment #5) > I have similar errors with some Jabra Active 75t and Bose QC35 headphones as > well. FC-30 is bluez-5.52 could see lot of changes related to audio codec's. Would it be possible to verify if I prepare a test bluez build with 5.52 or the latest one ? Gopal.. (In reply to gopal krishna tiwari from comment #6) > (In reply to Josh Boyer from comment #5) > > I have similar errors with some Jabra Active 75t and Bose QC35 headphones as > > well. > > FC-30 is bluez-5.52 could see lot of changes related to audio codec's. Would > it be possible to verify if I prepare a test bluez build with 5.52 or the > latest one ? > > Gopal.. I'd be happy to test. I've ordered a set of Skullcandy Ink'd+ Active bluetooth earbuds that will arrive on Friday, will update with my findings. Confirmed, the new headphones also don't work: May 22 07:58:38 latitude7390 systemd[1752]: Starting Bluetooth OBEX service... May 22 07:58:39 latitude7390 obexd[33542]: OBEX daemon 5.50 May 22 07:58:39 latitude7390 dbus-daemon[1954]: [session uid=1000 pid=1954] Successfully activated service 'org.bluez.obex' May 22 07:58:39 latitude7390 systemd[1752]: Started Bluetooth OBEX service. May 22 07:58:39 latitude7390 kernel: Bluetooth: RFCOMM TTY layer initialized May 22 07:58:39 latitude7390 kernel: Bluetooth: RFCOMM socket layer initialized May 22 07:58:39 latitude7390 kernel: Bluetooth: RFCOMM ver 1.11 May 22 07:58:43 latitude7390 bluetoothd[1341]: a2dp-sink profile connect failed for 38:F3:2E:6A:AF:C0: Protocol not available May 22 07:58:44 latitude7390 bluetoothd[1341]: a2dp-sink profile connect failed for 38:F3:2E:6A:AF:C0: Protocol not available May 22 07:58:44 latitude7390 bluetoothd[1341]: a2dp-sink profile connect failed for 38:F3:2E:6A:AF:C0: Protocol not available May 22 07:58:45 latitude7390 bluetoothd[1341]: a2dp-sink profile connect failed for 38:F3:2E:6A:AF:C0: Protocol not available May 22 07:58:45 latitude7390 bluetoothd[1341]: a2dp-sink profile connect failed for 38:F3:2E:6A:AF:C0: Protocol not available May 22 07:58:46 latitude7390 bluetoothd[1341]: a2dp-sink profile connect failed for 38:F3:2E:6A:AF:C0: Protocol not available May 22 07:58:46 latitude7390 bluetoothd[1341]: a2dp-sink profile connect failed for 38:F3:2E:6A:AF:C0: Protocol not available Sorry, forgot these in the above comment: May 22 07:58:59 latitude7390 kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) May 22 07:59:15 latitude7390 kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) May 22 07:59:30 latitude7390 kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) May 22 07:59:47 latitude7390 kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) May 22 08:00:03 latitude7390 kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) May 22 08:00:19 latitude7390 kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) May 22 08:00:34 latitude7390 kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) May 22 08:00:51 latitude7390 kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) May 22 08:01:07 latitude7390 kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) I tried this from bluetoothctl also, same behavior (and journal logs) I observed from using GNOME Settings: $[bluetooth]# power on Changing power on succeeded $[bluetooth]# scan on Discovery started [CHG] Controller D0:C6:37:66:B5:74 Discovering: yes [NEW] Device 61:6F:95:74:9E:B6 61-6F-95-74-9E-B6 [CHG] Device 38:F3:2E:6A:AF:C0 RSSI: -58 [CHG] Device 38:F3:2E:6A:AF:C0 TxPower: 4 [CHG] Device 38:F3:2E:6A:AF:C0 Class: 0x00240418 [CHG] Device 38:F3:2E:6A:AF:C0 Icon: audio-card [CHG] Device 61:6F:95:74:9E:B6 RSSI: -93 [CHG] Device 61:6F:95:74:9E:B6 RSSI: -85 $[bluetooth]# pair 61:6F:95:74:9E:B6 Attempting to pair with 61:6F:95:74:9E:B6 [CHG] Device 61:6F:95:74:9E:B6 Connected: yes Failed to pair: org.bluez.Error.AuthenticationFailed [CHG] Device 61:6F:95:74:9E:B6 Connected: no [DEL] Device 61:6F:95:74:9E:B6 61-6F-95-74-9E-B6 [NEW] Device 61:6F:95:74:9E:B6 61-6F-95-74-9E-B6 Alright, so if I kill pulseaudio first and then do this from bluetoothcmd it does work and I'm able to play music through the headphones: $ pulseaudio -k $ bluetoothctl $[bluetooth]# paired-devices Device 38:F3:2E:6A:AF:C0 Ink'd+ Active Device 20:9B:A5:83:87:64 SoundBuds Slim+ $[bluetooth]# connect 38:F3:2E:6A:AF:C0 Attempting to connect to 38:F3:2E:6A:AF:C0 [CHG] Device 38:F3:2E:6A:AF:C0 Connected: yes Connection successful [CHG] Device 38:F3:2E:6A:AF:C0 ServicesResolved: yes $[Ink'd+ Active]# trust 38:F3:2E:6A:AF:C0 Changing 38:F3:2E:6A:AF:C0 trust succeeded (In reply to Adam Miller from comment #12) > Alright, so if I kill pulseaudio first and then do this from bluetoothcmd it > does work and I'm able to play music through the headphones: > > $ pulseaudio -k > $ bluetoothctl > $[bluetooth]# paired-devices > Device 38:F3:2E:6A:AF:C0 Ink'd+ Active > Device 20:9B:A5:83:87:64 SoundBuds Slim+ > $[bluetooth]# connect 38:F3:2E:6A:AF:C0 > Attempting to connect to 38:F3:2E:6A:AF:C0 > [CHG] Device 38:F3:2E:6A:AF:C0 Connected: yes > Connection successful > [CHG] Device 38:F3:2E:6A:AF:C0 ServicesResolved: yes > $[Ink'd+ Active]# trust 38:F3:2E:6A:AF:C0 > Changing 38:F3:2E:6A:AF:C0 trust succeeded Ok, Seems like we have some issue with pulseaudio. I'll try to check. Gopal.. (In reply to Josh Boyer from comment #7) > (In reply to gopal krishna tiwari from comment #6) > > (In reply to Josh Boyer from comment #5) > > > I have similar errors with some Jabra Active 75t and Bose QC35 headphones as > > > well. > > > > FC-30 is bluez-5.52 could see lot of changes related to audio codec's. Would > > it be possible to verify if I prepare a test bluez build with 5.52 or the > > latest one ? > > > > Gopal.. > > I'd be happy to test. Hi Josh, Can you please try and check with disabling pulseaudio and later tries to connect the device. Does this helps. Gopal.. Hi Josh/Adam, Here is the brew build with bluez - 5.52 https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28758846 See if solves the issue. Gopal.. Gopal,
It doesn't look like that build actually produced any RPMs
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28758948
https://brewweb.engineering.redhat.com/brew/rpmlist?buildrootID=5995506&type=built
-AdamM
(In reply to Adam Miller from comment #16) > Gopal, > It doesn't look like that build actually produced any RPMs > > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28758948 > https://brewweb.engineering.redhat.com/brew/ > rpmlist?buildrootID=5995506&type=built > > -AdamM Seems its deleted due timeline .. Just fired another build. Please find below https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28854288 regards, Gopal.. Looked to be cleaned up again. The retention period used to be longer for scratch builds. My apologies for not grabbing it the day you rebuilt. Can you do so one more time? (In reply to Josh Boyer from comment #18) > Looked to be cleaned up again. The retention period used to be longer for > scratch builds. My apologies for not grabbing it the day you rebuilt. Can > you do so one more time? Np's. Please check http://brew-task-repos.usersys.redhat.com/repos/scratch/gtiwari/bluez/5.52/4.el8/x86_64/ If you can download it from here else will fire the build again. Gopal.. Yep, that works. I'll test them this afternoon and also try killing pulseaudio as noted above. (In reply to Josh Boyer from comment #20) > Yep, that works. I'll test them this afternoon and also try killing > pulseaudio as noted above. Sure. Thanks Gopal.. I was able to get the jabra headphones to pair, but they don't show up as having a mic in Gnome settings: Jun 02 07:51:10 zod bluetoothd[1160]: /org/bluez/hci0/dev_70_BF_92_CA_B4_76/sep1/fd0: fd(25) ready Jun 02 07:51:07 zod systemd-logind[1278]: Watching system buttons on /dev/input/event19 (70:BF:92:CA:B4:76) Jun 02 07:51:07 zod kernel: input: 70:BF:92:CA:B4:76 as /devices/virtual/input/input20 Jun 02 07:51:03 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:51:03 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jun 02 07:51:03 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:51:01 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:51:00 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy The Bose don't pair at all: Jun 02 07:47:46 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:44 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:44 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jun 02 07:47:33 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:30 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:30 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jun 02 07:47:24 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:21 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:21 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jun 02 07:47:20 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:20 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jun 02 07:47:19 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:19 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jun 02 07:47:17 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:17 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jun 02 07:47:17 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:14 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:14 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jun 02 07:47:12 zod systemd[1524]: Started Mark boot as successful. Jun 02 07:47:12 zod systemd[1524]: Starting Mark boot as successful... Jun 02 07:47:12 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:09 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:09 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jun 02 07:47:09 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:09 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jun 02 07:47:08 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:08 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jun 02 07:47:06 zod bluetoothd[1160]: connect error: Device or resource busy (16) Jun 02 07:47:06 zod bluetoothd[1160]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jun 02 07:46:32 zod systemd[1524]: Started Bluetooth OBEX service. This is already better than before. I haven't had a chance to try killing pulseaudio. (In reply to Josh Boyer from comment #22) > I was able to get the jabra headphones to pair, but they don't show up as > having a mic in Gnome settings: > > Jun 02 07:51:10 zod bluetoothd[1160]: > /org/bluez/hci0/dev_70_BF_92_CA_B4_76/sep1/fd0: fd(25) ready > Jun 02 07:51:07 zod systemd-logind[1278]: Watching system buttons on > /dev/input/event19 (70:BF:92:CA:B4:76) > Jun 02 07:51:07 zod kernel: input: 70:BF:92:CA:B4:76 as > /devices/virtual/input/input20 > Jun 02 07:51:03 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:51:03 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > Jun 02 07:51:03 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:51:01 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:51:00 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > > The Bose don't pair at all: > > Jun 02 07:47:46 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:44 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:44 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > Jun 02 07:47:33 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:30 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:30 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > Jun 02 07:47:24 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:21 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:21 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > Jun 02 07:47:20 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:20 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > Jun 02 07:47:19 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:19 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > Jun 02 07:47:17 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:17 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > Jun 02 07:47:17 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:14 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:14 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > Jun 02 07:47:12 zod systemd[1524]: Started Mark boot as successful. > Jun 02 07:47:12 zod systemd[1524]: Starting Mark boot as successful... > Jun 02 07:47:12 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:09 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:09 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > Jun 02 07:47:09 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:09 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > Jun 02 07:47:08 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:08 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > Jun 02 07:47:06 zod bluetoothd[1160]: connect error: Device or resource busy > (16) > Jun 02 07:47:06 zod bluetoothd[1160]: Unable to get Headset Voice gateway > SDP record: Device or resource busy > Jun 02 07:46:32 zod systemd[1524]: Started Bluetooth OBEX service. > > This is already better than before. I haven't had a chance to try killing > pulseaudio. Does bose headphone works with fc-30 ? Another do you see anything in dmesg output ? Gopal.. (In reply to gopal krishna tiwari from comment #23) > > Does bose headphone works with fc-30 ? Another do you see anything in dmesg > output ? No idea. I don't have a fedora machine handy. There is nothing additional in dmesg. I do remember long long ago when I first got those headphones that the firmware is very quirky and I only got it working on Fedora 20-something after a lot of fiddling. I'm more than willing to ignore them and just focus on the jabra pair. The jabra headphones work fine except for the mic not showing up, and I'll try messing with pulseaudio later. (In reply to Josh Boyer from comment #24) > (In reply to gopal krishna tiwari from comment #23) > > > > Does bose headphone works with fc-30 ? Another do you see anything in dmesg > > output ? > > No idea. I don't have a fedora machine handy. There is nothing additional > in dmesg. > > I do remember long long ago when I first got those headphones that the > firmware is very quirky and I only got it working on Fedora 20-something > after a lot of fiddling. I'm more than willing to ignore them and just > focus on the jabra pair. The jabra headphones work fine except for the mic > not showing up, and I'll try messing with pulseaudio later. Sure, Thanks. Regards, Gopal Hi Adam, I've checked the pulseaudio killing. If I understood it correctly it's basically to sync if in case its failing to pick up the device. Please let me know if you need anything else from my side. Gopal.. (In reply to gopal krishna tiwari from comment #26) > Hi Adam, > > I've checked the pulseaudio killing. If I understood it correctly it's > basically to sync if in case its failing to pick up the device. > > Please let me know if you need anything else from my side. > > Gopal.. Closing this out for now. Please feel free to re-open. Thanks Josh/Adam for your help on this. Gopal.. Wait... why is this closed? I only had success using the bluez scratch build you provided. Is that change going to land in RHEL via some other bug? (In reply to Josh Boyer from comment #28) > Wait... why is this closed? I only had success using the bluez scratch > build you provided. Is that change going to land in RHEL via some other bug? Aaah my fault .. I took it completely wrongly :( .. My apologies. I'll import the changes soon. Gopal.. Saw this on RHEL 8.2 desktop. Seemed to be competing with itself over LE-Bose (low energy BT). [CHG] Device 4C:87:5D:9D:42:AF Name: Bose NC 700 HP [CHG] Device 4C:87:5D:9D:42:AF Alias: Bose NC 700 HP [CHG] Device 4C:87:5D:9D:42:AF Connected: no [CHG] Device 4C:87:5D:9D:42:AF Connected: yes [CHG] Device 4C:87:5D:9D:42:AF Connected: no [DEL] Device 4C:87:5D:9D:42:AF Bose NC 700 HP [NEW] Device 4C:87:5D:9D:42:AF Bose NC 700 HP [CHG] Device 4C:87:5D:9D:42:AF Connected: no [DEL] Device 4C:87:5D:9D:42:AF Bose NC 700 HP [NEW] Device 4C:87:5D:9D:42:AF LE-Bose NC 700 HP [CHG] Device 4C:87:5D:9D:42:AF TxPower: 4 [CHG] Device 4C:87:5D:9D:42:AF Name: Bose NC 700 HP [CHG] Device 4C:87:5D:9D:42:AF Alias: Bose NC 700 HP That was a few days ago. Updated OS via Yum, and it seems to work better. Now at: [root@jwesterd ~]# uname -a Linux jwesterd.remote.csb 4.18.0-193.13.2.el8_2.x86_64 [root@jwesterd ~]# modinfo bluetooth | grep ver version: 2.22 description: Bluetooth Core ver 2.22 rhelversion: 8.2 srcversion: C1E5FD94B66FFFE03FCB76F vermagic: 4.18.0-193.13.2.el8_2.x86_64 SMP mod_unload modversions Now I seem to be able to stop / start Bluetooth (from GUI), at least on output side. When I pair the headset (output) with bluetooth, the mic (input) has to be manually set. Once mic (input) is selected (Headphone Bose NC 700 HP), Profile is in "Headset Handsfree" mode which only provides static/noise over mono under "test speakers". Picking on the profile reveals "High Fidelity Playback (A2DP Sink)" which enables the Right/Left Speaker Tests to work as expected. THen its all good! Using Bluejeans parrot https://bluejeans.com/111/ as my test. I haven't been able to reproduce the situation initially reported against RHEL-8.2.0, even with the Anker SoundBuds Slim+ noted in comment 3. Adam, if you get a chance, could you try testing against a recent build of RHEL-8.3.0 and see if it fixes the issue for you? If this fixes it for you I will get this verified. It's been a couple of weeks and I haven't heard anything. If the fix doesn't work please reopen this bug. For now, I'm going to verify this as SanityOnly since I ran testing against RHEL-8.3.0-20200812.n.0 awhile back against numerous Bluetooth headsets and speakers and had no issue pairing, connecting, or playing audio through them. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (bluez bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4562 This problem affects RHEL8.3 still. Here's a fix that makes it work better. It's question of loading pulse audio bluetooth discovery module too early, so user doesn't have access to it. This solution helps me get the Bose QC35 to work, after I hammer the bluetooth connect button few times. But without this fix, there is no chance to get them working: https://gist.github.com/freyes/dfc3f5232526a62bbc09adc816e0477d " Source: https://g751jy.wordpress.com/about/parrot-zik-bluetooth-headset/ https://bbs.archlinux.org/viewtopic.php?id=194006 Cached: http://webcache.googleusercontent.com/search?q=cache:4stTobIXSD0J:https://g751jy.wordpress.com/about/parrot-zik-bluetooth-headset/+&cd=3&hl=en&ct=clnk&gl=us Bug and possible solution: actually I found a bug in that make the headset unusable, it seems that the pulse audio module: module-bluetooth-discover works only if started after the X11 session is up. So I have a workaround. Edit the file: /etc/pulse/default.pa and comment out (with an # at the beginning of the line) the following line: #load-module module-bluetooth-discover now edit the file: /usr/bin/start-pulseaudio-x11 and after the lines: if [ x”$SESSION_MANAGER” != x ] ; then /usr/bin/pactl load-module module-x11-xsmp “display=$DISPLAY session_manager=$SESSION_MANAGER” > /dev/null fi add the following line: /usr/bin/pactl load-module module-bluetooth-discover This way the Pulse audio’s Bluetooth modules will not be downloaded at boot time but after x11 is started. " Problem with it is that this gets overwritten in my laptop while RHEL pulls updates, and I need to manually fix it again. I created a new bug: https://bugzilla.redhat.com/show_bug.cgi?id=1901027 (In reply to Ilkka Tengvall from comment #40) > I created a new bug: https://bugzilla.redhat.com/show_bug.cgi?id=1901027 Thanks Ilkka for creating new BUG. Gopal.. |