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.
Bug 1263638 - not able to pair sennheiser MM100 headset
Summary: not able to pair sennheiser MM100 headset
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: bluez
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.3
Assignee: Don Zickus
QA Contact: Ken Benoit
URL:
Whiteboard:
Depends On: 1296616
Blocks: 1274397 1313485
TreeView+ depends on / blocked
 
Reported: 2015-09-16 10:35 UTC by Tomas Pelka
Modified: 2016-11-04 05:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 05:37:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
bluetooth debug log (131.29 KB, text/plain)
2015-09-23 14:28 UTC, Tomas Pelka 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:2402 0 normal SHIPPED_LIVE bluez bug fix update 2016-11-03 13:56:00 UTC

Description Tomas Pelka 2015-09-16 10:35:43 UTC 
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
Comment 2 Don Zickus 2015-09-22 20:20:35 UTC 
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
Comment 3 Tomas Pelka 2015-09-23 14:28:31 UTC 
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
Comment 11 Don Zickus 2016-08-04 21:13:41 UTC 
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
Comment 12 Ken Benoit 2016-09-08 17:17:51 UTC 
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.
Comment 13 Vladimir Benes 2016-09-13 07:51:43 UTC 
I am able to pair with sennheiser mm100, use A2DP sink and control volume/balance.
Comment 15 errata-xmlrpc 2016-11-04 05:37:39 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.