Bug 1001338 - Migrate to Bluez 5
Summary: Migrate to Bluez 5
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: release-notes
Version: devel
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Pete Travis
QA Contact: Fedora Docs QA
Depends On: 998563
TreeView+ depends on / blocked
Reported: 2013-08-26 22:35 UTC by Pete Travis
Modified: 2014-01-26 22:05 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 998563
Last Closed: 2014-01-26 22:05:38 UTC

Attachments (Terms of Use)

Description Pete Travis 2013-08-26 22:35:07 UTC
+++ This bug was initially created as a clone of Bug #998563 +++

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.

Discussion at https://lists.fedoraproject.org/pipermail/devel-announce/2013-August/001227.html

Please create entries for this Change in the Release Notes.

Comment 1 Pete Travis 2013-10-05 22:16:54 UTC
draft content at https://fedoraproject.org/wiki/Documentation_Networking_Beat

Comment 2 Carl van Tonder 2014-01-06 15:29:29 UTC
There is at least one regression as a result of this change -- bluetooth audio devices can no longer be used in "headset" (HSP) mode -- see bug #1045548.

This regression is documented in the draft release notes for Pulseaudio 5.0[0], which say (in "Notes for packagers"):

> PulseAudio now supports BlueZ 5, but only the A2DP profile. BlueZ 4 is still the only way to make HSP/HFP work.

This notice should, I think, be in the F20 release notes to avoid unpleasant surprises.

[0] http://www.freedesktop.org/wiki/Software/PulseAudio/Notes/5.0/

Comment 3 Pete Travis 2014-01-26 22:05:38 UTC
Carl, it is unfortunate that we (I) missed this when composing the release notes.  I think the way forward is working to get the functionality added; for future releases, your help in creating the release notes *before* release would be welcome.

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