Bug 1582282 - Bluez fails to pair with the Bose QC35 headphones
Summary: Bluez fails to pair with the Bose QC35 headphones
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 28
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Don Zickus
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-24 17:26 UTC by 結城イヴ
Modified: 2019-05-28 20:38 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 20:38:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Log of the error from bluetoothctl, btmon, etc. (5.26 KB, text/plain)
2018-05-24 17:26 UTC, 結城イヴ
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1620636 0 None None None 2018-05-24 17:26:26 UTC

Description 結城イヴ 2018-05-24 17:26:26 UTC
Created attachment 1441172 [details]
Log of the error from bluetoothctl, btmon, etc.

Description of problem:
Bluez is unable to pair with the Bose QC35 headphones regardless of ControllerMode (dual, bredr, etc.). 

Version-Release number of selected component (if applicable):
5.49-3.fc28

How reproducible: Always

Steps to Reproduce:
1. Place the Bose QC35s in pairing mode by holding 
2. Use the GUI or bluetoothctl to attempt to scan for and attempt to pair the QC35s.
3. Pairing will fail, sometimes immediately, sometimes after a few seconds. 

Actual results: 
The pairing will fail and the headphones will not connect to the PC. I attached some debug output from bluetoothctl and btmon.

Expected results:
The Bose QC35s would pair correctly and be operable as they do in macOS, Windows, Android, iOS, etc.

Additional info:
* There's an unresolved bug report from 2016 about this exact issue on Launchpad, bug #1620636. 
* Some StackOverflow users on Fedora 22-24 reported success pairing by changing ControllerMode in /etc/bluetooth/main.conf to "breder", but this does not seem to work for me and others.

Comment 1 結城イヴ 2018-05-24 17:28:13 UTC
Additional info: This bug also seems to effect the Bose QC35 IIs.

Comment 2 Eric Smith 2018-05-24 22:09:53 UTC
I have had mixed results using a Bose QC35 II with Fedora 27 x86_64. The pairing worked fine. Sometimes I get audio routed to the headphones; sometimes I get silence. I did not change anything in /etc/bluetooth/main.conf, or manually edit any configuration files.

Comment 3 結城イヴ 2018-06-14 09:09:23 UTC
As expected, this bug persists in bluez-5.50-1.fc28.x86_64.

Comment 4 Ben Cotton 2019-05-02 19:19:18 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2019-05-02 21:35:11 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2019-05-28 20:38:56 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.