Bug 998563 - Migrate to Bluez 5
Summary: Migrate to Bluez 5
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Jaroslav Reznik
QA Contact:
Depends On:
Blocks: 1001338 1001339
TreeView+ depends on / blocked
Reported: 2013-08-19 14:16 UTC by Jaroslav Reznik
Modified: 2014-01-07 11:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1001338 1001339 (view as bug list)
Last Closed: 2013-12-18 14:01:23 UTC
Type: ---

Attachments (Terms of Use)

Description Jaroslav Reznik 2013-08-19 14:16:23 UTC
This is a tracking bug for Change: Migrate to Bluez 5
For more details, see: http://fedoraproject.org//wiki/Changes/Bluez5

BlueZ is the Linux Bluetooth stack for managing wireless Bluetooth devices. In Fedora 20, we are going to switch from BlueZ version 4 to version 5.

Comment 1 Jaroslav Reznik 2013-10-11 08:46:30 UTC
This message is a reminder that Fedora 20 Accepted Changes 100%
Completed Deadline is on 2013-10-15 [1].

All Accepted Changes has to be code complete and ready to be
validated in the Beta release (optionally by Fedora QA). Required
bug state at this point is ON_QA.

As for several System Wide Changes, Beta Change Deadline is a
point of contingency plan, all incomplete Changes will be 
reported to FESCo for 2013-10-16 meeting. In case of any
questions, don't hesitate to ask Wrangler (jreznik).

[1] https://fedoraproject.org/wiki/Releases/20/Schedule

Comment 2 Pavel Šimerda (pavlix) 2013-10-17 07:40:49 UTC
I'm very curious whether stuff like bluetooth PAN and bluetooth DUN will be still working or whether there will be regression in functionality.

Comment 3 Kalev Lember 2013-10-17 08:46:57 UTC
Pavel, see https://bugzilla.gnome.org/show_bug.cgi?id=701078#c49 and later comments for what's exactly implemented in NetworkManager.

Comment 4 Jaroslav Reznik 2013-12-18 14:01:23 UTC
Closing this bug as this Change was delivered in Fedora 20 release. Please, reopen in case of any issues you encounter regarding this Change completion.

Comment 5 Carl van Tonder 2014-01-06 15:35:03 UTC
This change removes support for bluetooth audio devices in "headset" (HSP) profile.

I can find no discussion of this regression in mailing list or IRC archives, in #1001338 or this bug, or on the Bluez5 feature page. I am curious as to how this task was completed without anyone mentioning this known limitation -- a QA group meeting in July raised the fact that the status of that feature was unknown, but nothing seems to have been said since then.

It's probably way too late now, but the feature page had a "Contingency plan" for "major bluetooth-related regressions" -- whose decision was it to declare that there were no "major .. regressions"?

Comment 6 Jaroslav Reznik 2014-01-07 11:28:25 UTC
It's the decision of Change owner unless concerns are raised (in time) to FESCo.

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