Red Hat Bugzilla – Bug 1263638
not able to pair sennheiser MM100 headset
Last modified: 2016-11-04 01:37:39 EDT
Description of problem:
Sep 16 12:24:40 dhcp131-186.brq.redhat.com bluetoothd: No agent available for request type 0
Sep 16 12:24:40 dhcp131-186.brq.redhat.com bluetoothd: device_request_pin: Operation not permitted
Sep 16 12:24:40 dhcp131-186.brq.redhat.com bluetoothd: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This is working with bluez-5.29
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. :-(
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
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.
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.
I am able to pair with sennheiser mm100, use A2DP sink and control volume/balance.
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.