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:
Sep 16 12:24:40 dhcp131-186.brq.redhat.com bluetoothd[878]: No agent available for request type 0
Sep 16 12:24:40 dhcp131-186.brq.redhat.com bluetoothd[878]: device_request_pin: Operation not permitted
Sep 16 12:24:40 dhcp131-186.brq.redhat.com bluetoothd[878]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Version-Release number of selected component (if applicable):
bluez-5.23-4.el7
bluez-libs-5.23-4.el7
How reproducible:
100%
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
should pair
Additional info:
This is working with bluez-5.29
Hi,
Can you stop the bluetoothd
systemctl stop bluetooth.service
and start by hand with logging?
/usr/sbin/bluetoothd -n -d
and attach the logs?
Updating to bluez-5.29 is not going to work ath this stage. :-(
Cheers,
Don
Created attachment 1076248[details]
bluetooth debug log
Tied multiple times pairing and connecting the device.
Got also segfault when removing paired device but I can't reproduce.
Device address: 00:07:04:CE:0F:2B
Hi,
The problem seems to be there is no agent registered to handle the PIN transaction. If you start
a gnome-shell, I believe blueman becomes that agent and can accept the PIN request thus allowing
your headset to pair.
Updating to the latest RHEL-7.3 bluez (bluez-5.39) should resolve the segfaul you are seeing.
Cheers,
Don
I don't have a pair of these headphones to test with. Tomas, is everything working ok with the latest Bluetooth updates? I've run some Bluetooth testing on my side of things with a Bluetooth speaker, sending files to a cell phone, using a cellphone as a Bluetooth modem, and using a cellphone as a Bluetooth mic and everything seems to be running correctly. Just want to make sure everything is working ok with the headphones so I can mark this as verified.
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, 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://rhn.redhat.com/errata/RHEA-2016-2402.html