Bug 1534406 - bluez 5.48-1 breaks support for some Bose headphone models
Summary: bluez 5.48-1 breaks support for some Bose headphone models
Keywords:
Status: CLOSED DUPLICATE of bug 1534857
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 27
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-01-15 07:50 UTC by Gianfranco Cecconi
Modified: 2018-02-09 14:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-09 14:49:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gianfranco Cecconi 2018-01-15 07:50:49 UTC
Description of problem:

I upgraded to bluez 5.48-1 yesterday using a routine dnf update. Since then my Bose QC3 (mark I) and have stopped working correctly. My Bose SoundSport seem to be fine. 

Version-Release number of selected component (if applicable):

bluez 5.48-1 from packages

How reproducible:

Always

Steps to Reproduce:

Issue no. 1

1. Turn the headphones on for the first time after upgrading bluez

Actual results:

You will hear from the automated voice in the headphones, in a quick sequence, three successful attempts to connect that fail immediately after, after which the headphone stops trying. 

Issue no. 2

1. After experiencing issue no. (1), unregister the device and register it again
2. Play some music (tried this with both Spotify and Rhythmbox)

Actual results:

The music plays according to these cycles: a) a few seconds ok, b) a few seconds with gaps, c) one or two seconds accelerated, d) back to (a) 

Expected results:

In both cases, the headphones connect and play the music.

Thanks!

Comment 1 Gianfranco Cecconi 2018-01-16 06:53:57 UTC
A quick note that everything works again when downgrading to bluez 5.47-2, the previous version packaged for Fedora. Sorry I hadn't tested this yesterday.

Comment 2 Gianfranco Cecconi 2018-01-28 13:30:07 UTC
A quick update to share that I am experiencing the issue no. 2 identically also on a Bose SoundLink Revolve. Worst news is that I'm having the issue with bluez 5.47-2, too and dnf downgrade does not allow me to test even older versions easily.

Comment 3 Gianfranco Cecconi 2018-01-29 06:56:49 UTC
Upgraded back to 5.48-1 and the problem appears to be fixed on the QC3. I don't know what to think at this point. Perhaps the act of installing / uninstalling cleans up something that may cause the issue described above?

Comment 4 Dominik 'Rathann' Mierzejewski 2018-02-01 10:07:59 UTC
Possibly a duplicate of bug 1534857.

Comment 5 Gianfranco Cecconi 2018-02-01 11:30:19 UTC
@Domink no it is not a duplicate, there's nothing about what I describe in issue no. 2 in the other bug. Thanks.

Comment 6 Bastien Nocera 2018-02-09 14:49:34 UTC

*** This bug has been marked as a duplicate of bug 1534857 ***


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