Feature changed by: Stefan Behlert (sbehlert)
Feature #315090, revision 36
Title: Upgrade to Bluez 5
Requested by: Jeffrey Cheung (jeffreycheung)
Partner organization: openSUSE.org
Description:
BlueZ 5 come with numerous new features, API simplifications and other
improvements. With this release BlueZ only supports the new Bluetooth
Management kernel interface that was introduced in Linux 3.4, so
essentially this is the minimum kernel requirement for BlueZ 5. For Low
Energy support at least kernel version 3.5 is needed. The new major
version indicates that the API is not backwards compatible with BlueZ
4, which means that any applications, agents, etc will need to be
updated. The BlueZ internal test scripts and tools have naturally
already been updated to support the new API.
The BlueZ version in SLE11 SP3 is BlueZ 4.99 which mean that regardless
of new features, and improvements, we have to upgrade definitely.
+ References:
+ Packages: ofono
Discussion:
#1: Frederic Crozat (fcrozat) (2013-06-25 16:26:22)
Bluez 5 can be installed in parallel with Bluez4, allowing applications
not ported to BlueZ 5 API to work properly
#2: Frederic Crozat (fcrozat) (2013-07-02 16:53:42) (reply to #1)
it looks like I was a bit optimistic. You can only have one BlueZ
installed (4 or 5) and they aren't API compatible, which requires
having all BT applications moved to BlueZ 5..
#3: Jeffrey Cheung (jeffreycheung) (2013-08-05 12:06:33)
So, can this fate proceed ?
#4: Ludwig Nussel (lnussel) (2013-08-07 10:34:47) (reply to #3)
We are past feature freeze with Milestone 4 now. I suppose this will
affect the desktops so please evaluate the potential fallout and
discuss on the Factory mailinglist whether it's still possible to fix
the affected packages.
#5: Jeffrey Cheung (jeffreycheung) (2013-08-07 11:15:59) (reply to #4)
Hi Ludwig Nussel,
Thanks of reminder. I already send email to factory mailing list. The
current status is that RD finished the x86-64 part but i386 not yet.
#6: Stefan Seyfried (seife) (2013-08-07 17:00:41)
Also note that the bluez library is deprecated with bluez5, so if we
want to do it "right", we should not pass --enable-library to
configure. The consequence if this is that almost everything that uses
bluez will break, though :-)
#7: Jeffrey Cheung (jeffreycheung) (2013-08-08 15:39:18) (reply to #6)
Thanks and RD acknowledged your comment. We may miss upgrade at
openSUSE 13.1 and wait for 13.2 next year.
However, we will keep working for SLE12.
#12: Petr Tesařík (ptesarik) (2013-08-20 14:03:06)
FWIW the Bluetooth stack is currently broken in Factory. At least I
cannot get my BT headset to work. We would have to make our own patch
to fix this bug (backporting from upstream is hard because of API
changes).
I'm afraid the maintenance cost in SLE12 lifetime is prohibitively
high, not even daring to think about security monitoring.
#16: Al Cho (acho-novell) (2013-08-21 15:02:41) (reply to #12)
Hi Petr, Thanks for your comment. and Would you file a bug to me about
your headset doesn't work ? ( or the bug is already there? ) I would
fix it.
Thanks, AL
#20: Petr Tesařík (ptesarik) (2013-08-23 12:46:13) (reply to #16)
The failure seems to be somewhat related to the HCI hardware, not to
the bluez version. I only wanted to mention it as an example, but it
wasn't a good one after all.
Nevertheless, I still believe that providing L3 support for an outdated
bluez version for years is too much effort. Moreover, this would be
wasted effort, while helping to update dependent packages (in upstream)
pays off.
#13: Ondrej Holecek (oholecek) (2013-08-20 15:05:24)
Note that current PulseAudio (4.0) does not support Bluez5. PulseAudio
5.0 with initial Bluez5 support was planned to release around upcoming
GNOME 3.10 (end of September AFAIK) but freeze was postponed so this
target was missed.
#14: Petr Tesařík (ptesarik) (2013-08-21 11:50:56) (reply to #13)
This is sweet. So, the same Lennart who repeatedly introduced
incompatible changes in the infrastructure and asked everybody to
adapt, has been unable for over a year to adapt his fine software to a
similar change in the infrastructure he's using... Why am I surprized?
*sigh*
#18: Joey Lee (joeyli) (2013-08-23 07:06:48)
Thanks for the comments from Petr, Ondrej and Scott. Per Scott's
comment, looks Gnome will move to support BlueZ 5. If there doesn't
have KDE in SLE-12, then I think move to BlueZ 5 in SLE-12 is make
sense.
This FATE highly dependent to the development progress of desktop UI(e.
g. Gname, KDE) but not just replace the BlueZ package and take care the
bluetooth driver in kernel. So, I suggest add desktop engineering
leader and Gnome experts to this FATE to collaborative work.
#19: Jeffrey Cheung (jeffreycheung) (2013-08-23 15:42:17)
Very well, AL, please watch closely the gnome development. Hi Scott,
can you provide your member which AL can cowork with.
#21: Jeffrey Cheung (jeffreycheung) (2013-08-25 23:28:54)
Add Some current mail thread from openSUSE factory mailing list
(1) From Dimstar / Dominique Leuenberger