- 1 Migrate to Bluez 5
- 1.1 Summary
- 1.2 Owner
- 1.3 Current status
- 1.4 Detailed Description
- 1.5 Benefit to Fedora
- 1.6 Scope
- 1.7 Upgrade/compatibility impact
- 1.8 How To Test
- 1.9 User Experience
- 1.10 Dependencies
- 1.11 Contingency Plan
- 1.12 Documentation
- 1.13 Release Notes
Migrate to Bluez 5
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.
- Name: Bastien Nocera, Kalev Lember, and the desktop SIG
- Email: email@example.com, firstname.lastname@example.org
- Release notes owner:
The BlueZ project recently released BlueZ version 5. Compared to BlueZ version 4, the new release brings new features and improvements, however it is also accompanied by a significant API change. The BlueZ versions 4 and 5 are not parallel installable, and we need coordination between various parts of Fedora to switch over at the same time.
This is coming late after the Change Proposals Submission Deadline. As this affects various critical parts of the distribution (KDE, GNOME, NetworkManager, pulseaudio), we wanted to be sure it is feasible to switch everything over at the same time, and were considering postponing it to Fedora 21. However, upstreams have made good progress with porting over to BlueZ 5 and we feel it would be beneficial for Fedora to switch over during the Fedora 20 timeframe.
Benefit to Fedora
This keeps the Bluetooth stack in Fedora up to date. BlueZ 4 is no longer maintained upstream; switching to BlueZ 5 ensures we can get all the latest upstream bug fixes and enhancements.
BlueZ 5 uses a D-Bus API that's not compatible with BlueZ 4 and as such, management applications and a number of libraries and daemons need to be ported.
- Proposal owners:
This is a change affecting many parts of the distribution. The proposal owners, supported by the rest of the Desktop SIG, are going to take care of updating the BlueZ package to version 5 and porting over gnome-bluetooth, NetworkManager, and PulseAudio packages.
- KDE SIG:
The bluetooth stack for KDE is BlueDevil. It has a git branch with BlueZ 5 support and the Fedora KDE SIG will handle updating the package to a git snapshot.
- Desktop SIG:
For GNOME 3.10, Gustavo Padovan and Bastien Nocera have been porting gnome-bluetooth, NetworkManager and PulseAudio to BlueZ 5, and the Fedora Desktop SIG will ensure these get updated to the BlueZ 5 versions in Fedora.
- NetworkManager team:
... will ensure the relevant NetworkManager changes land in Fedora 20.
- MATE team:
mate-bluetooth has not received much upstream attention recently and is likely to not get ported to BlueZ 5 in time for F20. However, the Fedora MATE maintainers are looking into switching back to using gnome-bluetooth, and creating a panel applet for MATE that uses gnome-bluetooth underneath. An initial prototype is available at https://github.com/NiceandGently/bluetooth-panel-applet
- Other developers:
Bluez4 and Bluez5 are not parallel-installable, and incompatible, so other applications relying on Bluez4 will need to be ported by their respective maintainers.
- Release engineering:
No release engineering coordination required.
- Policies and guidelines:
No changes needed in the packaging guidelines.
See the following mailing list post for details and discussion for affected packages: https://lists.fedoraproject.org/pipermail/devel/2013-June/184334.html
BlueZ ships a daemon and provides two main interfaces for applications to use it:
The library ABI hasn't changed, so the upgrade/compatibility impact should be minimal. Applications using the libbluetooth library should be able to continue working without needing code changes or rebuilds.
BlueZ D-Bus API
The D-Bus API has had major changes. Most major consumers should be ported over during the Fedora 20 timeframe, with one exception:
Blueman is abandoned upstream and is going to be dropped from Fedora 20. The following mailing list post includes the relevant details: https://lists.fedoraproject.org/pipermail/devel/2013-August/187223.html
How To Test
Testing the change requires having Bluetooth capable hardware. Major functionality should keep working without regressions, compared to BlueZ 4 in Fedora 19.
User experience should change minimally.
This requires coordination between the kernel team, the Desktop team, the KDE team, and various other package maintainers. The proposal owners will handle the coordination.
If the release blocking desktops have major bluetooth related regressions by the time of the Fedora 20 Beta Change Deadline, then FESCo and the proposal owners may enact a contingency plan to revert the BlueZ 5 related changes and go back to BlueZ 4. In that case, we'll likely want to keep using BlueZ in the Rawhide branch and only revert the changes in Branched (F20).
In addition, the upstream GNOME release team is also keeping an eye open for regressions, and will revert back to BlueZ 4 for GNOME 3.10 (due in September) if there are major regressions in either GNOME, NetworkManager or PulseAudio.
1) Bump bluez package's epoch in both Branched and Rawhide branches 2) Revert bluez back to version 4.101 in F20 and stick with 5.x in F21 3) Switch NetworkManager, PulseAudio, gnome-bluetooth, BlueDevil back to using BlueZ 4 in the F20 branch 4) Send a notice to fedora-devel-announce, asking other package maintainers to switch back to BlueZ 4 in the F20 branch
LWN introduction to BlueZ 5: http://lwn.net/Articles/531133/
BlueZ 5 porting guide: http://www.bluez.org/bluez-5-api-introduction-and-porting-guide/
Fedora 20 uses BlueZ version 5 for managing Bluetooth devices. The new BlueZ release includes significant API changes and all major desktops have been ported over.