Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
As a laptop user, I can't get my Bose QC35 headset to connect over BT using gnome bluetooth settings.
Version-Release number of selected component (if applicable):
RHEL 8.2 and RHEL 8.3
rpm -qf /usr/bin/start-pulseaudio-x11
pulseaudio-module-x11-13.99.1-1.el8.x86_64
How reproducible:
Steps to Reproduce:
1. Pair the headset
2. Press connect from bluetooth menu
Actual results:
BT device does not connect, or briefly shows connect and disconnects.
Expected results:
Audio jump to BT.
Additional info:
Similar bug: https://bugzilla.redhat.com/show_bug.cgi?id=1830397#c39
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.
Affects rhel 8.4 as well. I just upgraded from 8.3, and I'm having the same issue again. Need to edit the files manually again.
Comment 9RHEL Program Management
2022-05-24 07:27:24 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.